unclecheese

@Nathan It supports OR matching for the value, but not the field. Adding disjunctive clauses quickly sends you down a rabbit hole, because now you introduce things like nested conditions, and it gets really messy. For the first pass at this, it seemed sufficient to just do AND. I’d be curious how other graphql APIs deal with the syntax of this. Have you seen any examples?

unclecheese

@Nemanja Karadzic Can you provide the context in which that happens? It often means the graphql client was expecting a JSON response from a query and got plain text (e.g. a verbose error)

unclecheese

Yeah, I had to do this with graphql-forms , too. The form schema provides an arbitrary data property that is just ¯_(ツ)_/¯

unclecheese
  1. SilverStripe using [/getting-started/composer](Composer)

That’s not the right markdown syntax, is it? 😮

unclecheese

Its my next major project, starting any day now. Can you put your hand up to test it? And by test it, I mean make a good faith effort to get it into a production site?

unclecheese

In which case you’ll need “...on SilverStripeFile” wrapping your field list.

unclecheese

Because if there’s an inheritance chain, the query will resolve to a union of all the members in the chain.