Andrew Hyndman

Yeah, I'm seeing this too now. This will be because the version of GraphQL is locked to an old version (0.9.3) and in the most recent versions, this syntax was...

The issue is that `gql` still only supports `[email protected]`. https://github.com/Mayank1791989/gql/blob/master/package.json#L41 Support for descriptions was only added in `[email protected]`. https://github.com/graphql/graphql-js/releases/tag/v0.12.0 I believe that @Mayank1791989 is working on a v3 branch which...

[clabot:check]

Thanks for the quick response, @syrusakbary. I'm beginning to suspect that the source of the non-determinism I'm seeing is `graphene_django`. We don't have any hand-coded types, but we are using...

@syrusakbary I believe we've managed to isolate the two sources of non-determinism that we were experiencing. The first is Mutation arguments. The second occurs when a DjangoObject type has multiple...

I stumbled on this issue the other day, and decided to try my hand at it. I am not certain it can be extended to all valid CSV separators, but...

@AriaMinaei What scenarios are you worried about breaking inexact object types in?

Huh, wow. You're right, that's an issue! That feels like a bug in flow, itself. Maybe related to this one? https://github.com/facebook/flow/issues/2405 Intuitively, I would have expected an inexact object type...

In the meantime, some possible workarounds. [Try Flow: Make everything inexact](https://flow.org/try/#0PTAEAEDMBsHsHcBQAXAngBwKagIKgLygDeAPqANQCGAXKAM7IBOAlgHYDmoJAvgNwoZsAIQLEKAI1oMWHUH0QCsoAMKiioAHRacAGk1aRc-okgBXVgGNkzWK1CYAHlivKAFBdrKAlFKZtORIigwYyYyKaMdhYa4oh8QA) I can't reason about why Flow thinks property **b** has become optional in this first scenario, though. [Try Flow:...

I just thought I'd share a cheap user-space workaround that my team came up with, in case it's helpful for anyone else. ```js const { AsyncResource } = require('node:async_hooks') /**...