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

Move Message Types to Their Respective Crates #25

Open
1 task
mccallofthewild opened this issue Aug 23, 2022 · 2 comments
Open
1 task

Move Message Types to Their Respective Crates #25

mccallofthewild opened this issue Aug 23, 2022 · 2 comments

Comments

@mccallofthewild
Copy link
Collaborator

mccallofthewild commented Aug 23, 2022

As raised in #24 (comment), the consolidation of message types into a single crate makes contracts less readable. Futhermore, it may cause cargo to behave inefficiently, recompiling all reverse dependencies every time a the ultra-base crate changes.

Definition of Done

  • All message types moved from ultra-base to their respective contracts/<contract>/msg.rs
@mccallofthewild mccallofthewild changed the title Move Types to Their Respective Crates Move Message Types to Their Respective Crates Aug 23, 2022
@mccallofthewild
Copy link
Collaborator Author

Considering closing this, as many contracts are interdependent and we cannot write them all at once, so having all message types in one place enables us to develop using message types that don't have implementations yet.

@mccallofthewild
Copy link
Collaborator Author

WIP in: mccallofthewild/flatten-types

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant