-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Standardize modules stucture #4438
Comments
Looks good to me! Although I think we should rename |
This looks reasonable to me, but a couple questions:
i.e: for a module named "claim":
Also, with this layout, a simple dapp could be implemented as a single module. When is it preferable to go with multiple modules over a single one? I'm guessing if a module provides general functionality and could be re-used, then it should be it's own thing. |
1.) I agree, hence I recommended
This depends on the context of the app/module. Ideally, all modules should as extensible and modular as possible. Even if an app could be implemented using a single module -- it should be a module. |
Updated. Querier will exist in |
We should use Golang's special |
|
Closing via #4618. Please refer to the updated module spec for the most updated version of the standard. |
Summary
Standardize folders and location of files across SDK modules.
Problem Definition
This allows for other features to be created from this standard (eg #4191, Swagger file autogenerated from module, etc).
Some modules don't follow the structure as described by @alexanderbez
Proposal
Ensure modules follow and comply the proposed standard tree. Maybe add check with CI
For Admin Use
The text was updated successfully, but these errors were encountered: