fix(api): Allow null associations on non-required fields. #2440
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
#2431
Description of changes:
Don't throw an exception if an association field is null when creating a mutation.
This is because it is valid for the field to be null if it's not required. Codegen does not mark such fields as required in the generated models. If it is required then attempting to submit the mutation with a null value will result in an error response.
How did you test these changes?
Checked that the schema provided in the original issue could now create a Note class without a customer association.
Documentation update required?
General Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.