2 ms·
and I strongly agree with GP because those arguments <https://graphql.org/learn/schema/#arguments https://graphql.org/learn/schema/#arguments> can get to be ins
by mdaniel 2y ago
and I strongly agree with GP because those arguments <https://graphql.org/learn/schema/#arguments https://graphql.org/learn/schema/#arguments> can get to be insaneo with anything other than simplistic "episode: EMPIRE"; I regrettably can't link directly to it but https://docs.github.com/en/graphql/reference/objects#:~:text=A%20list%20of%20issues%20that%20have%20been%20opened https://docs.github.com/en/graphql/reference/objects#:~:text... shows that stuff can start to be more than the interior field selection, to say nothing of schemas that define complex typed arguments e.g.
type Starship {
id: ID!
name: String!
}
type CaptainQuery {
captains(starshipFilter: [Starship!]): [Starship]
}
# leading to
{
captains(starshipFilter: [{name: "Alpha"},{id: "cafebabe"}]) { id }
}
which I recognize is most often fixed via variables but when the hello-world examples call it out, something has gone awry https://docs.github.com/en/graphql/guides/forming-calls-with-graphql#:~:text=the%20syntax%20can%20get%20unwieldy https://docs.github.com/en/graphql/guides/forming-calls-with...
- Izkata 2y agoThat has some json-ish embedded inside it, but the query itself still isn't json. And even the embedded part isn't valid json without quoting the keys.
- doctor_eval 2y agoBut if you write the query to use variables, the variables are json. JSON is great (though not perfect) as an interchange format, but it’s decidedly not a query language.