feat: add dynamic schema to postgrest client #455
Merged
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.
Resolves #280
What kind of change does this PR introduce?
New feature
What is the current behavior?
See discussion on #280
The current behavior is that the
PostgrestClient
is created with a schema passed into the constructor. The class instance cannot reference tables or rpc calls for any other schemas unless a new instance is created.What is the new behavior?
A single class instance exposes a facade method to reference other schemas:
Type inference for responses also work, assuming a
Database
type has been supplied:Table schema:
Compare without
.schema('personal')
:Additional context
Assuming this PR is accepted, this PR supabase/supabase-js#828 could be modified like so:
This would allow the following:
Add any other context or screenshots.