Add inflection comment directive to the SQL schema in the README #579
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
Update the SQL schema to include the inflection comment directive, especially since the screenshot below has inflected field and type names.
|
I did realize there is documentation available in the main Supabase docs, which has the same content as the Still, this proposed change should still be valid since screenshot shows inflected values! |
imor
approved these changes
Feb 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What kind of change does this PR introduce?
This PR updates the SQL schema in the TL;DR section of the README to include the inflection comment directive, especially since the screenshot below has inflected field and type names.
While I was trying to figure out if there was a way to do this using supabase / pg_graphql, the README in this repo was confusing because the screenshot clearly showed what I wanted (camelCase and PascalCase in my GraphQL schema), yet I wasn't getting that in my own project. Because this feature is super useful but not very well documented (at least visibility-wise), I think it would benefit folks to just show that this feature is available front and center.
I will probably follow up with another PR / doc suggestion for the main supabase documentation as well.