This repository has been archived by the owner on Aug 26, 2021. It is now read-only.
Fix validation when passing an interface to the injects list. #222
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I admit that this fix is clumsy. The core problem is that
the 'injects' list serves double duty: it includes types that
we can call ObjectGraph.get() on (could be interfaces) and also
types that we call ObjectGraph.inject() on (can't be interfaces).
The right fix is to rethink the way Dagger internally tracks
and links these keys.