Add Documentation for ApplyTransforms, and Add Resources to Each and PgSelect Docs #2163
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
In my usage of Grafast at my workplace for the past few months, I've fallen in love with it. I've also obtained some learnings that I wish I had read in the docs. This is focused mainly around modifying the keys/values returned from a
PgSelect
. We have been working through the unique case of having to support a legacy GraphQL schema while not wanting that to affect our database design. This meant writing plans to resolve fields that required changing the returned keys and values from the DB a lot.Hopefully, these changes might help others that run into similar use-cases.
Question that prompted this: #2161
Performance impact
Security impact
Checklist