Skip to content
This repository was archived by the owner on Jan 10, 2025. It is now read-only.

⬆️ support graphql 15.x#1978

Merged
vsumner merged 5 commits intomainfrom
support-graphql-15.x
Aug 24, 2021
Merged

⬆️ support graphql 15.x#1978
vsumner merged 5 commits intomainfrom
support-graphql-15.x

Conversation

@marutypes
Copy link
Contributor

@marutypes marutypes commented Jul 28, 2021

Description

Our version ranges meant that projects with dependencies that want graphql@15.x would have (possibly worrisome) duplicate graphql dependencies.

Checklist

  • I have added a changelog entry, prefixed by the type of change noted above (Documentation fix and Test update does not need a changelog as we do not publish new version)

),
]
: [];
try {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this now throws an error rather than returning null, so we need to wrap it in a try to get at that.

[Error: Error parsing 'packages/graphql-validate-fixtures/test/fixtures/malformed-query/queries/Another.graphql':

Syntax Error: Expected {, found Name "name"]
Syntax Error: Expected "{", found Name "name".]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some minor error message changes also meant we needed to regen our snapshots

Object {
"keyPath": "generation",
"message": "value does not match enum Generation (available values: FIRST, SECOND, THIRD)",
"message": "Value \\"SEVENTH\\" does not exist in \\"Generation\\" enum.",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these snapshots changed more because they come from the try / catch we added (they used to be a custom error)

]
: [];
try {
return type.parseValue(value) == null
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we still try to do this so that we support 14.x

@marutypes
Copy link
Contributor Author

hmm looks like we got some TS errors, weird since I didn't see those running build locally. I'll look into them

@marutypes marutypes force-pushed the support-graphql-15.x branch 2 times, most recently from 26c726f to 8bff4f6 Compare August 16, 2021 18:44
@marutypes marutypes marked this pull request as ready for review August 16, 2021 18:55
@marutypes marutypes requested a review from a team August 16, 2021 18:55
@marutypes marutypes force-pushed the support-graphql-15.x branch from bb73839 to e6b5084 Compare August 16, 2021 19:32
Copy link
Contributor

@dahukish dahukish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@vsumner vsumner force-pushed the support-graphql-15.x branch from e6b5084 to 53294f3 Compare August 24, 2021 19:56
@vsumner vsumner merged commit 1b79556 into main Aug 24, 2021
@vsumner vsumner deleted the support-graphql-15.x branch August 24, 2021 21:16
@shopify-shipit shopify-shipit bot temporarily deployed to production August 26, 2021 14:49 Inactive
@shopify-shipit shopify-shipit bot temporarily deployed to michenly-beta August 26, 2021 17:50 Inactive
@shopify-shipit shopify-shipit bot temporarily deployed to gem August 30, 2021 18:42 Inactive
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants