Anthony Miller

That is so exciting to hear @NathanFallet ! Thanks for letting us know! We will definitely revisit this when we get back to this part of the project on our...

We highly recommend uploading files using another mechanism and then setting up your mutations to take an identifier to access the uploaded data elsewhere. See: https://www.apollographql.com/docs/ios/mutations/#an-important-caveat-about-file-uploads File uploads with GraphQL...

Thanks for the report! > You know I see schemaName used as the namespace elsewhere, so yeah, maybe it just needs to be used on the fragment types as well....

As I've been working on #2424, I'm realizing we need to prefix with schema name for other types as well. When implementing this (hopefully tomorrow!), we need to prefix: -...

Realizing as I test this, that it only works when the Fragments are in the schema module. If the fragments are placed in your other targets, I don't really know...

Okay, I've come up with a few options for how to resolve this. I'm looking for feedback on how we should handle it before I can implement it, so I...

After further consideration, we've decided to make option 2a an **opt-in** solution. You can choose to use a field alias on a single conflicting name. If you want to handle...

This should actually already be fixed in the `release/1.0` branch. `Object`, `Interface`, and `Union` are now namespaced inside of the schema as `MySchema.Objects.Dog`, etc. @jimisaacs Can you confirm if this...

This is going to be related to #516. I'm going to try to find some time to look into how we can make this week at some point in the...

> At the same time, my code was making the assumption that a fetch or mutation result handler is guaranteed to be called. I agree with this assumption. Even if...