feat: add ChangeSchema function to supabase.Client #18
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.
Add a ChangeSchema function to supabase Client that wraps the postgrest ChangeSchema method
What kind of change does this PR introduce?
Feature: Add a function to supabase Client
What is the current behavior?
There is no way to change schema once the Client is initialised
postgrest field is private which makes it impossible to use the same client for different schemas
What is the new behavior?
Adds a ChangeSchema method that wraps the postgrest method of the same name. This makes it easy to change the schema as per the requirements of the business logic