Tag optional filters in a parseable way #262
Labels
priority/low
There is a consensus that this have low priority to sort out.
status/has-concrete-suggestion
This issue has one or more concrete suggestions spelled out that can be brought up for consensus.
We've already gone to some effort to make sure examples are tagged correctly as
:filter:
, which is really helpful. My suggestion is to also be clearer when marking optional features of the filter language. Currently we are very clear in the text, but it would be really helpful when generating examples for validation to either tag optional filters as e.g.:filter-optional
, or to just ensure that lines that contain optional filter examples are prefixed with "OPTIONAL:" in the text, as we do in many places.As a concrete example,
HAS ONLY
is introduced in the spec as:which could be reworded as:
The text was updated successfully, but these errors were encountered: