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: add nonScalarFields and arrayFields to schemas with mapped names #2689

Merged

Conversation

palpatim
Copy link
Member

@palpatim palpatim commented Jul 3, 2024

Description of changes

The relevant commits in this PR are from cherry picked from @kekami, as first proposed in #2627

This PR resolves merge conflicts and provides a base for verifying with E2E tests.

Issue #, if available

#2581

Checklist

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

use non-mapped table name to generate array/non-scalar fields on
relational queries

✅ Closes: #2581
update snapshots for graphql-name-mapping-transformer
add tests to ensure array/non-scalar fields are properly set on
relational objects
@palpatim palpatim requested a review from a team as a code owner July 3, 2024 17:23
@palpatim palpatim merged commit 4feb898 into main Jul 3, 2024
7 checks passed
@palpatim palpatim deleted the kekami-graphql-relational-transformer/fix-non-scalar-fields branch July 3, 2024 20:53
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.

4 participants