Neo4jGraphQL contaminates the global scope/and or mergeSchemas about graphql HOT 8 CLOSED

@darrellwarde The Trello card is on a private board so I can't see it. Can you provide some context here?

from graphql.

Sorry @lirbank, it is a private board and my comment was posted automatically when I referenced this issue from our Trello instance.

Essentially, the plan is to remove our custom scalars which override the default Int and Float scalars. They're not working as expected in a number of places, so we will replace the (de)serialization of these values in other ways.

from graphql.

Thanks @darrellwarde! I know this is hard to answer but this is a complete blocker for us so if there is any chance you can provide an indication of when this may be fixed that would be a great help, so we can plan accordingly. Do you think it is days, weeks or months we're talking about? Big thanks in advance!

from graphql.

@lirbank meanwhile have you tried routing your external resolvers through Neo4jGraphQL instead of merging them through Apollo Server? Documentation here.

from graphql.

Thanks @darrellwarde! I know this is hard to answer but this is a complete blocker for us so if there is any chance you can provide an indication of when this may be fixed that would be a great help, so we can plan accordingly. Do you think it is days, weeks or months we're talking about? Big thanks in advance!

I completely understand your frustration, and thank you for your patience.

I really don't like committing to timelines, so please take this with a pinch of salt and not as a commitment. But we work in development phases, the next one being 5 weeks long and starting next week. We'll be agreeing on its content today, but we're hoping it will include addressing a couple of key bugs, including this one. All going well, it will be released either during the phase, or at the end of the phase, depending on our order of attack.

We really don't want to leave users hanging for months on this one.

from graphql.

@colinskow That's a good idea! I tried to do this with the, now deprecated, neo4j-graphql-js package and we couldn't get it to play (was some issue with GraphQL interfaces that we have in our base schema) but if this works with Neo4jGraphQL that'd be great! Totally forgot about this approach since we shelved it once before, thanks for bringing it up!

@darrellwarde Thanks a bunch, that's very helpful!

from graphql.

@darrellwarde - Just curious if this got a commitment for this sprint/dev cycle? Like @lirbank, this is a show stopper for us. I can let it go for a couple more weeks, but we go live on June 1st with our "alpha". Right now, I've created a workaround by writing a custom cypher to handle pagination, but this isn't a solution that can be long-term.

from graphql.

A fix (hopefully!) for this has now been merged, and will be released shortly (aiming for tomorrow). Please do test and feel free to reopen this ticket if it hasn't addressed your problems! 🙂

from graphql.