This would be really useful for us as well. I thought this was part of RFC: Allow multiple unique fields in graphql schema due to (emphasis mine):
We can filter the results using multiple id fields. getQuery will now accept many fields which have
@id field.
All of them will be connected usingAnd
filter in resulting query.
To clarify, the existing support for multiple @id
fields requires each field to be unique by itself and the “AND filtering” would mostly be a no-op (unless you passed two conflicting IDs that don’t actually exist as a pair)?