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
Right now, generated code is bloated into the namespace where macros are used. There are also strange limitations on naming of the modules for traits, which creates a place for mistakes.
I would prefer to isolate things a bit. All generated things should go to sv module (so if we #[contract], it would have things generated as sv::ExecMsg, sv::QueryMsg, etc). This way, rules about how to avoid naming collisions would be easy: single contract/interface call per module, but we eventually want the module to be named however the user wants to. Additionally "if you want to use sylvia, do not create sv modules yourself).
Additionally, I want to rename all tests-related generated modules to mt - we want to keep them short to be easy to type around.
The text was updated successfully, but these errors were encountered:
Right now, generated code is bloated into the namespace where macros are used. There are also strange limitations on naming of the modules for traits, which creates a place for mistakes.
I would prefer to isolate things a bit. All generated things should go to
sv
module (so if we#[contract]
, it would have things generated assv::ExecMsg
,sv::QueryMsg
, etc). This way, rules about how to avoid naming collisions would be easy: single contract/interface call per module, but we eventually want the module to be named however the user wants to. Additionally "if you want to use sylvia, do not createsv
modules yourself).Additionally, I want to rename all tests-related generated modules to
mt
- we want to keep them short to be easy to type around.The text was updated successfully, but these errors were encountered: