chore: upgrade GraphQL builder from 1.x to 2.x - #694
Conversation
The @Coerce schema directive (PR #692) now handles all known type-mismatch patterns (quantity/seller Int→String, category id String→Int, geoCoordinates Float→String) surgically at the field level. The strict coercion introduced by graphql@2.x is therefore safe — all 35 @Coerce unit tests pass. Co-authored-by: Cursor <cursoragent@cursor.com>
…ilder 2.x GraphQL builder 2.x requires the @auth directive on every query and mutation. All fields are marked with @auth(scope: PUBLIC) to preserve the same behaviour as 1.x, where queries without @auth were public by default. Also adds `scalar Upload` declaration required by the 2.x builder. All 864 unit tests pass. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
Co-authored-by: Cursor <cursoragent@cursor.com>
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
2 participants
What problem is this solving?
Builder
2.xrequires@authon every query and mutation. The previous upgrade attempt (#687) was reverted in #690 due to strict variable coercion errors — not because of this requirement. That root cause was fixed by the@coercedirective in #692, so the upgrade is safe to land now.What changed?
manifest.json:"graphql": "1.x"→"graphql": "2.x"graphql/schema.graphql:@auth(scope: PUBLIC)added to all queries and mutations;scalar Uploaddeclaration addedAll fields use
scope: PUBLIC, preserving the same public-by-default behaviour as1.x.How to test it?
Run
./test-errors-regression.shagainst a linked workspace — all 14 regression cases should pass.Related
Re-introduces the GraphQL builder portion of #687.
Depends on the coercion fix from #692.
Made with Cursor
Made with Cursor