warn that SQL Editor does not reproduce JWT context for auth-dependent view validation
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- sql, supabase
- Domain
- authentication, databases, documentation
Research direction
Locate the Supabase agent skill's verification guidance covering SQL Editor checks, views, or auth-dependent queries. Add a warning that SQL Editor lacks the application JWT, require testing in the authenticated client context or with independent base-table control queries, and ensure coverage tests do not use the filtered view as their sole oracle.
Written by the indexing model from the issue text.
Description
user-feedback: warn that SQL Editor does not reproduce JWT context for auth-dependent view validation
This is feedback about the Supabase agent skill, not a Supabase product defect. A view whose administrative branch depended on is_app_admin()/auth.uid() was validated from SQL Editor. Because that execution had no application JWT, auth.uid() was NULL and the view returned only the public subset. Structural assertions over the same filtered view returned true, creating a false sense of complete coverage. Please extend the verification guidance to require auth-dependent queries to be tested in the actual client authentication context, or against independent base-table control queries. It would also help to warn that SQL Editor is not equivalent to an authenticated Data API request and that coverage tests should not reuse the potentially faulty view as their sole oracle.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/agent-skills
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
supabase/agent-skills#586 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#585 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
supabase/agent-skills#583 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
supabase/agent-skills#582 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#581 ·
All issues in supabase/agent-skills
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100