-
Notifications
You must be signed in to change notification settings - Fork 73
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: disallow Gen 1 Patterns in GraphQL SDL schema. #1719
Conversation
🦋 Changeset detectedLatest commit: 2d115d9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Couple small comments. My main concern is that this is a breaking change even if the product team doesn't want to release it as such. Do we have data around how many customers have a gen 1 schema in gen 2? Should we print a warning saying that this behavior will be removed in a future major version instead?
schema, | ||
}); | ||
assert.throws(() => dataFactory.getInstance(getInstanceProps), { | ||
message: 'Failed to instantiate data construct', |
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.
Can we throw an error message that explains what is not supported and how to fix it?
.changeset/unlucky-otters-hide.md
Outdated
@@ -0,0 +1,5 @@ | |||
--- | |||
'@aws-amplify/backend-data': patch |
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.
'@aws-amplify/backend-data': patch | |
'@aws-amplify/backend-data': minor |
Problem
Customers can use Gen 1 patterns in GraphQL SDL string schema. This is not intentional.
Issue number, if available: N/A
Changes
Disallows usage of specific gen 1 patterns. See aws-amplify/amplify-category-api#2670 for list.
Corresponding docs PR, if applicable: aws-amplify/docs#7793
Validation
Checklist
run-e2e
label set.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.