Skip to content
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: set relational fields on many-to-many join table to optional #856

Closed
wants to merge 3 commits into from

Conversation

dpilch
Copy link
Member

@dpilch dpilch commented Jun 25, 2024

Description of changes

[BREAKING CHANGE]: set relational fields on many-to-many join table to optional

API change: aws-amplify/amplify-category-api#2660

Codegen Paramaters Changed or Added

N/A

Issue #, if available

N/A

Description of how you validated changes

  • Unit testing
  • E2E testing
  • TODO: check impact on runtime libraries

Checklist

  • PR description included
  • yarn test passes
  • Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)
  • Breaking changes to existing customers are released behind a feature flag or major version update
  • Changes are tested using sample applications for all relevant platforms (iOS/android/flutter/Javascript) that use the feature added/modified
  • Changes adhere to the GraphQL Spec and supports the GraphQL types type, input, enum, interface, union and scalar types.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@dpilch dpilch closed this Jun 27, 2024
@dpilch dpilch deleted the many-to-many-optional branch July 31, 2024 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant