-
Notifications
You must be signed in to change notification settings - Fork 826
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
Many-To-Many Connections have incorrect generated mutations for join model #3438
Comments
Hello @silvesteradamik the bug here is that the input type is requiring the |
Making the connected fields nullable solved the problem with filling the join connection table. However, there is now visible different issue: When fixing the issue, please check that the relations between the Editor and Post tables work bidirectional. |
This is only happening when conflict resolution is enabled, without that Transformer is behaving correctly. @silvesteradamik Please confirm that you've enabled conflict resolution for your API. |
Hi @attilah I can see the same error and I can confirm that I don't have conflict resolution enabled.
Error
|
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Describe the bug
Take example schema from page https://aws-amplify.github.io/docs/cli-toolchain/graphql#connection
Many-To-Many Connections and run the related example mutations.
The CreateLinks mutation fails.
This prevents filling up the join model table with data, thus making many to many connections not usable.
Execution of CreateLinks mutation fails:
Error message:
Amplify CLI Version
4.13.3
To Reproduce
Setup example schema and run example mutations
Expected behavior
Mutation CreateLinks is executed successfully.
Screenshots
none
Desktop (please complete the following information):
Additional context
The generated schema type CreatePostEditorInput contains post: PostInput! field which is probably the root cause of the issue.
The text was updated successfully, but these errors were encountered: