Uh oh!
There was an error while loading. Please reload this page.
docs: clarify omit is not a security feature - #622
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughDocumentation update to the omit configuration page adding a warning that omit is not a security mechanism and recommending access policies instead, plus revised wording describing scenarios for disabling query-time omit overrides. ChangesOmit documentation update
Estimated code review effort: 1 (Trivial) | ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Adds a warning callout to the omit docs clarifying that the omit feature (at all three layers — schema, client, and query) is not a security feature, but rather a convenient way to control the default set of fields returned during a query. Readers are pointed to access policies for protecting sensitive data.
Also removes the "for security reasons" phrasing from the
allowQueryTimeOmitOverridesection to stay consistent with this framing.🤖 Generated with Claude Code
Summary by CodeRabbit
omitsettings are not a security feature and should not be used to protect sensitive data.