Kyle Kashuba

In my case, I'm building both an app and a website plugin in the same project. The app is a form builder, and the website plugin is the form logic...

I don't believe this is a duplicate of #1047, as this error is being thrown when server-side rendering isn't being used whereas #1047 specifically mentions this behavior within NextJS. This...

To provide more context here, ideally I wouldn't see a type error here as evident in the query: In my schema, `userErrors` is typed as `[UserError!]!`. I could add non-null...

Yep, same here. Makes using TS not feasible. > Having same problem. For now, I am using old d.ts file from here https://github.com/citizenll/godot-typescript-starter. The README in that project states that...

Really looking forward to this, thank you for your efforts!

@wiredmatt That suggestion was discussed in detail in the linked issue: #13219 The TL;DR is essentially, it's not worth doing because there isn't sufficient existing practice/documentation/runtime behavior to facilitate such...

How about instead of all this, in your code you just return an `Error`, instead of throwing altogether. This is more reliable, easily supported by runtime behavior, requires less syntax...

My assumption is that it's to work around circular dependencies, as recommended in mobx-state-tree's docs: https://mobx-state-tree.js.org/tips/circular-deps Their reasoning is that since the data is type-safe at runtime, casting the `any`...

I've recently discovered MobX and am loving it a ton. I really want my team to adopt it but GraphQL raised a lot of questions that `mst-gql` elegantly provides great...