Make "value of" lines work with StreamSubject
.
#1224
Merged
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.
Make "value of" lines work with
StreamSubject
....by migrating off the deprecated no-arg
check()
overload.Usages of that method cause problems for "value of" lines.
Also, fill in a
typeDescriptionOverride
value forMultisetSubject
. This is largely a no-op, but it helps under GWT/J2CL (where we can't infer the type name).I left
IterableSubject
itself without atypeDescriptionOverride
, since it has subclasses outside the package, some of which may prefer the more specific names (which are normally automatically derived from theSubject
class's name—e.g.,AttributeListSubject
would result invalue of: attributeList.size()
). In hindsight, I guess that I could have given direct usages ofIterableSubject
atypeDescriptionOverride
(by makingStandardSubjectBuilder
pass one), but that seems like more effort than is worthwhile now that I've already tested this CL as it stands.RELNOTES=n/a