Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor tree messages to single up and single down container #385

Closed
dehann opened this issue Sep 10, 2019 · 3 comments · Fixed by #908
Closed

refactor tree messages to single up and single down container #385

dehann opened this issue Sep 10, 2019 · 3 comments · Fixed by #908

Comments

@dehann
Copy link
Member

dehann commented Sep 10, 2019

Introduction of CSM and tree initialization has resulted in multiple containers for the same thing.

@dehann
Copy link
Member Author

dehann commented Mar 3, 2020

xref #459

@dehann dehann modified the milestones: v0.x.0, v0.10.0, v0.10.1, v0.10.2 Mar 3, 2020
@dehann dehann modified the milestones: v0.10.2, v0.10.3, v0.10.4 Mar 18, 2020
dehann added a commit that referenced this issue Mar 20, 2020
@dehann dehann modified the milestones: v0.11.0, v0.11.x Mar 25, 2020
@dehann
Copy link
Member Author

dehann commented Mar 25, 2020

done in large part for v0.11.0 as intermediate types which are now common with parametric. Deferring further type updates until message channel containers and API too are consolidated.

@dehann
Copy link
Member Author

dehann commented Jul 19, 2020

up message containers consolidated in v0.13. Down container consolidation planned for v0.15

@dehann dehann modified the milestones: v0.15.0, v0.16.0 Aug 3, 2020
@dehann dehann closed this as completed Sep 18, 2020
@dehann dehann linked a pull request Sep 18, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant