fix: π generate array/non-scalar fields #2627
Closed
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.
use non-mapped table name to generate array/non-scalar fields on relational queries
β Closes: #2581
Description of changes
Fix issue where the generated AppSync DataResolverFn for relational SQL queries did not have
arrayFields
andnonScalarFields
correctly set, e.g.This was due to using the incorrect (mapped) tableName when generating these fields, e.g.
tasks
instead ofTask
Issue #, if available
#2581
Description of how you validated changes
Unsure if it could be tested in a better way
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.