Add Optional()
method to MatchQuery
#105
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.
node()
would crash, butnode(type='system', label='foo')
was okayapstra/two_stage_l3_clos_connectivity_template_integration_test.go
.optional
element toPathQuery
andMatchQuery
structs, so they know how to string-ify in match+optional contextMatchQuery
to it receivesQEQuery
implementations rather than onlyPathQuery
objects. Now we can write queries withmatch(match())
MatchQuery.Optional()
, which sets theoptional
flag on child queries