-
-
Notifications
You must be signed in to change notification settings - Fork 38
Update polymorphism.md #371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
When I initially read this, I thought that specifying the 'delegate' kind was the way to opt in to the feature. If someone is as careless as I was, they might not realize they are turning off access policies by only specifying one kind. I think this change will help the reader realize that each kind has to be specified
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThe pull request updates the Changes
Possibly related PRs
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
docs/guides/polymorphism.md (1)
131-131: Approved: Good clarification on specifying multiple kindsThe addition of the 'policy' kind alongside 'delegate' in the
enhancefunction call is a good clarification. It addresses the PR objective of preventing misunderstanding about specifying only one kind and potentially disabling authorization policies unintentionally.To further improve the documentation:
Consider adding a brief explanation after this code block to emphasize why specifying both 'delegate' and 'policy' kinds is important. For example:
Note: Specifying both 'delegate' and 'policy' kinds ensures that polymorphic relations and authorization policies are both enabled. Omitting either kind could lead to unexpected behavior in your application.This additional note would reinforce the importance of explicitly specifying each required kind.
|
Thank you for the fix @bbozzay ! Merging it now. |
When I initially read this, I thought that specifying the 'delegate' kind was the way to opt in to the feature. If someone is as careless as I was, they might not realize they are turning off authorization policies by only specifying one kind. I think this change will help the reader realize that each kind has to be specified
Summary by CodeRabbit
polymorphism.mdguide to clarify polymorphic relations in Prisma and ZenStack.