Filter out API lints according to pgrst.db_schemas
#71
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?
Several lints check if certain insecure object types are exposed publicly over APIs.
Historically, we have only used permissions of the
anon
andauthenticated
roles to determine if an object should be linted. We should also consider if the object is on the API's search pathpgrst.db_schemas
but that value was not available in the database.Now that supabase/supabase#25784 has merged, we can reference
pgrst.db_schemas
. This PR updates the relevant API lints to filter out entities that aren't on that API search pathThis change