CDI-662 Fix Instance.isResolvable() text #359
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
manovotn
reviewed
Dec 8, 2016
| * Identify the set of beans that have the required type and required qualifiers and are eligible for injection into the class into which the parent `Instance` was injected, according to the rules of typesafe resolution, as defined in <<performing_typesafe_resolution>>, resolving ambiguities according to <<unsatisfied_and_ambig_dependencies>>. | ||
| * The method `isUnsatisfied()` returns `true` if there is no bean found, or `false` otherwise. | ||
| * The method `isAmbiguous()` returns `true` if there is more than one bean found, or `false` otherwise. | ||
| * The method `isResolvable()` if there is exactly one bean found, or `false` otherwise. |
There was a problem hiding this comment.
isResolvable() if there -> isResolvable() returns true if there
|
I think it looks good |
|
LGMT |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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'm not going to fix the javadoc because we don't mention resolving ambiguities for any method there. I think to specify this only in the spec text.