feat(api-graphql): Add affected items in the errors object #11200
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.
Description of changes
Adding affected items when a relationship is deleted while querying for the data. The code takes the initial query data when non-null entities are encountered, generates a new query where all the entities will be present by returning only the id's from the query, and then compares the new response with the previous response to check for null entities. The respected null entities are then pushed back in the response.items array.
Issue #, if available
aws-amplify/amplify-category-api#3233
Description of how you validated changes
I checked the query with the schema table the customer was facing and other tables where non-nullable error messages could be shown and then compared the queries with and without the null returned attributes.
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.