refactor!(postgrest, supabase): make schema
variable private and rename useSchema()
to schema()
#737
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?
Currently the JS library uses
.schema()
to change the schema for calling APIs to non-public schema. However, the Dart library usesuseSchema()
, becauseschema
symbol was already taken by theschema
variable in postgrest.dart.This PR renames the
schema
variable to_schema
and.useSchema()
to.schema()
to align the public API with the JS library.What is the current behavior?
What is the new behavior?