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

Consider better structure of generated code #114

Closed
hashedone opened this issue May 5, 2023 · 0 comments
Closed

Consider better structure of generated code #114

hashedone opened this issue May 5, 2023 · 0 comments
Assignees
Labels
Milestone

Comments

@hashedone
Copy link
Collaborator

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.

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

No branches or pull requests

2 participants