Anthony Miller
Anthony Miller
@MatthewHendy, have you found any additional information on what could be causing this. It seems unlikely that this an issue with Apollo itself.
Closed due to inactivity.
Should we consider prioritizing this to get it in the 1.0 release? This is a pretty significant Developer Experience issue currently.
@trevorblades Do you know if this is something we should be pulling in? Now that docs are run from a separate project, I'm not sure if we even need renovate...
Actually, thinking about this. We do have an embedded TS library that uses NPM to pull in `graphql-js`. Perhaps we should be configuring renovate to look at that?
I really love this proposal, and I'm glad to see it being pushed forward. However it seems that we haven't yet come to a decision on how to handle list...
> Riffing on my original idea of repeated operators, and a few of the ideas above of introducing [] syntax directly, perhaps these could be combined in a way that...
I agree with @leebyron, that should probably be a validation error. I think considering this any type of type cast would open a lot of doors we probably don’t want...
I'm going back and forth on this, but I think we should allow the single `!` syntax at all times (only affecting the outermost element). **But if any nested depth...
I'm a big fan of allowing unions to implement interfaces. > Solution > A union should be considered an implementation of an interface if and only if each member type...