Ellen Shapiro

OK after pulling the Github schema and trying this myself, I think I figured it out: The problem is that you have two different properties **at exactly the same level**...

The recommended solution right now is aliasing one of the fields. It may be a perfectly valid GQL query, but unfortunately there's a difference between a) "a perfectly valid GraphQL...

> Not my repo so I can't alias. You should be able to alias in your GQL query - the alias should then get generated as the local typename. Unless...

Right that works for things that are different types, the issue here is that one thing is `Type`, the optional version of the type, and the other is `Type!`, the...

The error in your screenshot states the conflicting types are `NewMeeting` and `NewMeeting!` - those are optional vs. non-optional, which is why I was discussing optional vs. non-optional instead of...

@AttilaTheFun Can you confirm what version of the codegen and node you're using? If it's set up with the `run-bundled-codegen` script, that should print it out in the logs

Yeah I would have expected this to cause issues previously as well - it looks from the output like you're running codegen against the bundled node, so i don't think...

@AttilaTheFun Also, is this new behavior on 2.19.1, or do you recall when this behavior started?

In theory it should be deterministic (and in theory we'd get a lot more complaints about this if it weren't) - it seems like somewhere lower down the stack things...

Yeah, I generally agree with this thought. I'll have to figure out some kind of way to test it though...