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
Add a section about Types global namespace #97
Comments
@issuehuntfest has funded $20.00 to this issue. See it on IssueHunt |
@IssueHunt has funded $20.00 to this issue.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We would need a new section explaining how I designed cross-cutting
Types
global project namespace to be easily reused across the project as a module encapsulating all the types in the application.I leveraged the inversion of control principle, so instead of defining all the types in one place (in Types module, it's the responsibility of modules (which are owners of that particular type annotations) to extend the
Types
namespace.The main benefits are:
The text was updated successfully, but these errors were encountered: