技能 2026-09-30 14:16 UTC
launchworthy
由提交人 Wunderlandmedia 提交,主要更新类型为:问题缺陷修复与稳定性提升。提交说明:fix the Supabase view recipe in the over-exposure playbook。解决了已知运行时异常与边界错误,提升系统稳定性。
Commit提交信息原文
fix the Supabase view recipe in the over-exposure playbook Step 4 set security_invoker on the public view and then revoked all table access from anon and authenticated. An invoker view runs as the caller, so every read through it failed with permission denied, and Step 8 offered this as a safe fix. The new recipe revokes only table-wide select, grants select on the public columns, and keeps the invoker view over them. Tested against Postgres 16 (PGlite) with anon and authenticated roles: the old recipe fails exactly as described; the new one returns only the public columns and only the rows the policy allows (including a policy on a private column), refuses select * on the table, and leaves the owner's update working. - fixes/api-over-exposure.md: Step 4 rewritten, with what the change means for the app (named columns, writes that return rows, reading your own private fields on the server) and the pairing to avoid; Verify updated. - checklist.md (Domain 2): the Supabase over-exposure bullet describes the working pattern. - plugin.json: 1.1.3.