We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Module support is more natural if we can just supply our nested modules via the constructor.
Out of the box we get defaults and easy injection in tests.
Either convention based, for example, all data classes are parsed as modules parameter.type.jvmErasure.isData.
parameter.type.jvmErasure.isData
Or with annotation @Module
@Module
The text was updated successfully, but these errors were encountered:
AndreasVolkmann
No branches or pull requests
Module support is more natural if we can just supply our nested modules via the constructor.
Out of the box we get defaults and easy injection in tests.
Either convention based, for example, all data classes are parsed as modules
parameter.type.jvmErasure.isData
.Or with annotation
@Module
The text was updated successfully, but these errors were encountered: