-
Notifications
You must be signed in to change notification settings - Fork 296
GraphQL Query/Mutation Entity Field mapping support #1114
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Aniruddh25
reviewed
Jan 26, 2023
Aniruddh25
reviewed
Jan 26, 2023
…and mappings are utilized for REST testing
…. They have field names not compatible with graphql, special characters, spaces, and non compatible mappings.
Aniruddh25
approved these changes
Jan 30, 2023
abhishekkumams
approved these changes
Jan 30, 2023
Aniruddh25
reviewed
Jan 30, 2023
src/Service/Services/MetadataProviders/CosmosSqlMetadataProvider.cs
Outdated
Show resolved
Hide resolved
Collaborator
|
nit: fix PR description - tests have now been added. |
…ure/data-api-builder into dev/seleonar/graphQL_Mappings
Aniruddh25
approved these changes
Jan 30, 2023
Collaborator
Aniruddh25
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was an important change missing to add mappings functionality for a long time. Thanks for picking it up this milestone on top of doing the stored proc work!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why make this change?
mappingsconfiguration within GraphQL queries and mutations. This is support for aliasing an entity's fields (representative of database columns). This is important and useful for when a backing database has columns that violate GraphQL naming rules (e.g. prefixing a column name with double underscores (__) violates GraphQL reserved naming for introspection fields).What is this change?
How was this tested?
In progress.
Sample Request(s)
Database Column: "__typename" Alias used: "ExclusiveTypeName"
Sample Runtime Configuration "entities" section