Finalise connection filtering parameters
Implementations (Bonfire, hREA & potentially others) need to determine the appropriate filtering parameters for each record type and query edge.
Bridging schemas for *.filtering.gql
need to be created to provide a filter
parameter, and the fields of these input types should be well documented in the spec to indicate to implementations how they should behave. Some fields will have complex logic - for example, EconomicEvent.hasPointInTime
and EconomicEvent.hasBeginning
might want to be matchable by a parameter "startTime"
, and that parameter might want to accept logical operators like <=
, >=
, ==
etc.
A start has been made on planning.filtering.gql
, which can be used as a template for the other modules.
See related issues #72, #82 & #85 for more fine-grained decisions & discussion regarding filtering.