Skip to content
This repository has been archived by the owner on Jan 3, 2024. It is now read-only.

Support optional dependencies that can't be resolved for transitive reasons #68

Open
ghost opened this issue Sep 21, 2013 · 0 comments
Open

Comments

@ghost
Copy link

ghost commented Sep 21, 2013

Right now, a @Nullable dependency will be satisfied with null if it is not configured. We should consider extending this to allow it to be null if it is available via a default, but that default cannot be configured.

Another possibility is mark default binding rules as to-be-ignored if their dependencies cannot be satisfied.

*Originally reported by elehack on BitBucket

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

No branches or pull requests

0 participants