New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where clause not working with graphql: "15.0.0" #405
Comments
+1. Can confirm this. Where clause is ignored in graphql 15.0.0 |
This library needs to be changed to use the The extensions field was added here graphql/graphql-js#2097 |
This is already being worked on here: #418 |
Published |
when is this version going to be released? ive been using it since august with no issues |
Where clause should work in the v3 beta. Let us know if you have problems with it! |
How do I get v3 beta? We have an urgent need to get this working, join-monster with the latest graphql. Thanks! |
npm i join-monster@alpha
…On Thu, Nov 12, 2020 at 10:36 AM bwind00 ***@***.***> wrote:
How do I get v3 beta? We have an urgent need to get this working,
join-monster with the latest graphql. Thanks!
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#405 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB5LGECLF7SVUYOFOZ4RXLSPP6IDANCNFSM4MTAS7QA>
.
|
thanks, but that just installed 3.0.0-alpha2 which has the same problem with where mentioned above |
Sorry, an ingenious colleague figured out what we were doing wrong. In case it helps others, we had forgotten to encapsulate the where attribute in the new extensions attribute... |
Glad to hear! And just released as v3.0.0 |
I was just setting up a new project and noticed that using "graphql": "^15.0.0" didn't work well with the latest join-monster package.
Main issue that I noticed is that where clause wasn't honored.
Here are the packages that I was using:
Relevant parts of the code:
When using graphql 15, the sql statement that was produced inside the resolver didn't have the where clause.
As soon as I downgraded to 14.1.1 all worked fine.
The text was updated successfully, but these errors were encountered: