@cedarjs/permissions 8.0.0-canary.3570 → 8.0.0-canary.3571
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -3
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -1,9 +1,11 @@
|
|
|
1
1
|
# @cedarjs/permissions
|
|
2
2
|
|
|
3
3
|
Permissions for a Cedar app: who may do what, defined in one place. A role is a
|
|
4
|
-
named bundle of permissions.
|
|
5
|
-
|
|
6
|
-
|
|
4
|
+
named bundle of permissions.
|
|
5
|
+
|
|
6
|
+
Fields, services and components check a permission, never a role. So a role can
|
|
7
|
+
do exactly what its list says. A field added later is closed to a role until its
|
|
8
|
+
permission is on that role's list.
|
|
7
9
|
|
|
8
10
|
`yarn cedar setup permissions` sets this up. In an app with tenancy
|
|
9
11
|
(`yarn cedar setup tenancy`), `@cedarjs/tenancy` checks the same definitions
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@cedarjs/permissions",
|
|
3
|
-
"version": "8.0.0-canary.
|
|
3
|
+
"version": "8.0.0-canary.3571",
|
|
4
4
|
"repository": {
|
|
5
5
|
"type": "git",
|
|
6
6
|
"url": "git+https://github.com/cedarjs/cedar.git",
|
|
@@ -37,12 +37,12 @@
|
|
|
37
37
|
"test:watch": "vitest watch"
|
|
38
38
|
},
|
|
39
39
|
"dependencies": {
|
|
40
|
-
"@cedarjs/context": "8.0.0-canary.
|
|
41
|
-
"@cedarjs/graphql-server": "8.0.0-canary.
|
|
40
|
+
"@cedarjs/context": "8.0.0-canary.3571",
|
|
41
|
+
"@cedarjs/graphql-server": "8.0.0-canary.3571"
|
|
42
42
|
},
|
|
43
43
|
"devDependencies": {
|
|
44
44
|
"@arethetypeswrong/cli": "0.18.5",
|
|
45
|
-
"@cedarjs/framework-tools": "8.0.0-canary.
|
|
45
|
+
"@cedarjs/framework-tools": "8.0.0-canary.3571",
|
|
46
46
|
"concurrently": "9.2.5",
|
|
47
47
|
"publint": "0.3.25",
|
|
48
48
|
"tstyche": "5.0.2",
|