You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
mccallofthewild
changed the title
Move Types to Their Respective Crates
Move Message Types to Their Respective Crates
Aug 23, 2022
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.
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
ultra-base
to their respectivecontracts/<contract>/msg.rs
The text was updated successfully, but these errors were encountered: