Roman Ivantsov
Roman Ivantsov
well, yes, but mentioned in particular context - POST op, as far as I understood. As a result of discussion Subscriptions were removed from there, resulting in current situation when...
while I am all for it (not repeating fields in implementor interface), my biggest concern is backward compatibility; I just don't see how it can be done in backward compatible...
I think it's in-line with enum concept in programming languages like c# or java - enum is a list of names (!) or named int constants (in c#). I would...
> __typename is useless in a case where multiple discriminators are needed. can you please expand on this? and why this: ``` switch (weapon.__typeName) { ... ``` wouldn't work? why...
sorry but still not getting it. Why __typeName not discriminates enough?!
Suggesting simpler alternative: **Constant Fields** thanks for the explanation. Now I get it, kind of. So to sum it up - you need is a way to express that a...
> So version with constants is actually just a few characters longer that with literals but much simpler conceptually In your last sample, with strings, I think values should be...
by the way, the same can be achieved today, with a custom directive: \@ const(str: value)
directives on fields are not visible on fields - then let's fix the introspection! it is long overdue and does not make sense that some things are not available in...
I believe this stuff belongs to Relay or some other spec, not GraphQL. In real world models in general, having ID is not a universal thing, that each object has....