Alec Aivazis

I definitely plan on resolving it. My biggest hurdle right now is finding the time. if you have the time to explore a bit, let me know!

Just to update this issue with some conversations we've been having internally: since both of the bumps to support sveltekit 2 and svelte 5 will create major releases, we're going...

no, `[email protected]` will very likely be mostly version bumps. there might be some random clean up but we dont have anything major planned. anyway, i'm going to close this ticket...

Thanks for opening this! I think where we left off is this: > We could accept and string or an object. treat strings like global types and then make users...

Thanks for putting the reproduction together! I took a look and it seems like the reason the mutation isn't working is because the field that has been tagged with `@list`...

I'd be curious to see if there's any downside to having the extensions always present and avoiding the extra config. If you have some time to give it a shot...

I'm closing this issue since its gone a bit stale. feel free to let me know if you want to keep exploring options here

Our first react issue and its not a bug! I think you're onto something that I've been thinking about since I saw the isograph talk at GraphQL Conf. There _should...

Okay so i couldn't figure out how the composition could automatically work and still maintain valid graphql. For example, if a parent query has 2 fields that both point to...

Ah yea that could work in principle but I'm concerned about supporting the wide range of things that a user could do. The examples you show would be relatively straight...