-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Make operations permissions required #7848
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This comment was marked as resolved.
This comment was marked as resolved.
Commit history should be a good guide here in understanding actual changes vs updating all our various configs to comply with the change. TODO:
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 18c9db2:
|
bd6b647
to
45f49ef
Compare
8165962
to
ae8ddba
Compare
6250f6e
to
015bae2
Compare
91b9e92
to
ecadf21
Compare
ecadf21
to
18c9db2
Compare
When looking at operations permissions, we have observed that this can often be misconfigured.
We additionally don't want to rely on
true
orfalse
defaults that may be confusing or unexpected to users.As a result, we are changing
access.operations
on lists to be explicitly required.The basic change is the following:
To make this a bit easier however, we are adding two new options.
allows you to set all access controls at once, and
allows you to set all
operations
access controls for a list at once.New exports
We are providing three new helper exports to help out with this change so you can have code that reads well:
These functions should allow quickly applying access controls to lists. For example, to get the existing default access controls, you could do:
or
If you were setting access for create operations, you can quickly update to: