-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
fix(GraphQL Node): Change default request format to json instead of graphql #11346
fix(GraphQL Node): Change default request format to json instead of graphql #11346
Conversation
@ayatnkw at the moment these changes break the node for existing users, If you are changing default values you need to add a light version. If you look at the v1 Google Sheet node you can see where we did this for changing the default auth option from Service Account to OAuth. |
f8350aa
to
70c188a
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know! |
thanks for the feedback @Joffcom, made the changes you suggested and requested a review! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great so far :) Thanks for doing this. Could you also add a workflow test to test that we are indeed throwing an error when we're not using the JSON request format? Feel free to have a look at e71076c for some more information
d02aa52
to
df6a17e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added 2bc02b35d559595976bb77870fd7e99bfa124411
which throws the error requesting users to use the Request JSON format since response.errors
was undefined
(I don't think errors
is a field which exists on the response object actually)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Beyond that, LGTM :)
|
n8n Run #8786
Run Properties:
|
Project |
n8n
|
Branch Review |
node-1018-make-using-different-flavours-of-graphql-less-confusing
|
Run status |
Passed #8786
|
Run duration | 04m 45s |
Commit |
b63212ed48: 🌳 🖥️ browsers:node18.12.0-chrome107 🤖 ayatnkw 🗃️ e2e/*
|
Committer | Shireen Missi |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
2
|
Pending |
0
|
Skipped |
0
|
Passing |
489
|
View all changes introduced in this branch ↗︎ |
|
63fc4a5
to
b63212e
Compare
✅ All Cypress E2E specs passed |
…raphql (n8n-io#11346) Co-authored-by: Shireen Missi <[email protected]> Co-authored-by: Dana Lee <[email protected]>
…raphql (n8n-io#11346) Co-authored-by: Shireen Missi <[email protected]> Co-authored-by: Dana Lee <[email protected]>
…raphql (n8n-io#11346) Co-authored-by: Shireen Missi <[email protected]> Co-authored-by: Dana Lee <[email protected]>
Summary
This PR attempts to make the current Graphql node less confusing by
https://linear.app/n8n/issue/NODE-1018/make-using-different-flavours-of-graphql-less-confusing
It also changes the Query field from type
json
tostring
:https://linear.app/n8n/issue/NODE-1050/bug-json-field-for-graphql-nodes-for-query-field-is-wrong
Related Linear tickets, Github issues, and Community forum posts
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)