-
Notifications
You must be signed in to change notification settings - Fork 76
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
Don't autowire no-arg constructors, or make this configurable? #184
Labels
Comments
Adding compile-time configuration might be also useful to define a default trait implementation that should be wired. To do so, we may introduce a tag It would be worth considering additional parameters list for configuration tags, then we could use it as follows: autowire[ServiceA](useImplementation[ServiceB], useEmptyConstructors)(serviceC, serviceD) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Citing @mbore:
Something to consider - I think no-arg implementations might be common, but the argument with configuration is also a valid one.
Maybe we could somehow make this configurable - either support no-arg constructors or not? Or better, maybe the configuration could include packages from which we want to autowire, or a blacklist of packages which should never be autowired?
However, it's challenging to provide such configuration at compile-time - I suppose it would need to be somehow available at the type level?
The text was updated successfully, but these errors were encountered: