You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If any of the expected values are null then a matcher is still created and added to the composed matcher. Perhaps, if the value was an Optional then hasFeatureValue could return an Optional<Matcher> which and could then only append if not empty.
The text was updated successfully, but these errors were encountered:
A common use-case is to compose feature matchers only when their values are specified. The current API makes this hard.
Consider a simple example:
If any of the expected values are
null
then a matcher is still created and added to the composed matcher. Perhaps, if the value was anOptional
thenhasFeatureValue
could return anOptional<Matcher>
whichand
could then only append if not empty.The text was updated successfully, but these errors were encountered: