tree 8185c10857b9a0a51c0f33e01bc2143e288ecf59
parent 03f23d60e2079ea337a50eae3d6c21098151ce27
author Youssef Elghareeb <ghareeb@google.com> 1634727883 +0200
committer Youssef Elghareeb <ghareeb@google.com> 1634728519 +0200

Introduce a new submit requirement predicate that can be used in SRs

We added a #supportedForQueries method to the predicate class to let
sub-classes decide if they should be supported for queries. We also
create a new SubmitRequirementPredicate that is not supported for
queries.

We implemented the following changes:

* Updated QueryProcessor to throw an exception if any of the predicates
passed to #query has #supportedForQueries set to false.

* Created a new SubmitRequirementChangeQueryBuilder that extends
ChangeQueryBuilder. This new query builder supports all search operators
but can also add new operators. Any new operators should return a
"SubmitRequirementPredicate".

* Updated SubmitRequirementEvaluator to use the new query builder.

Currently, SubmitRequirementChangeQueryBuilder is still empty (i.e. did
not define any new operators). In later changes we'll add operators to
it.

Plugins contributing operands to the "has" or "is" predicates can now
return a SubmitRequirementPredicate, hence preventing it from being used
in search. The new operands will still work with submit requirement
expressions.

Change-Id: Id3581f4ad3eba84e2b6dbbee46694cd21beeefc4