@object-ui/fields 13.1.0 → 13.2.0
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/CHANGELOG.md +51 -0
- package/dist/index.cjs +4 -4
- package/dist/index.d.ts +1 -0
- package/dist/index.js +459 -351
- package/dist/widgets/CapabilityMultiSelectField.d.ts +11 -0
- package/dist/widgets/CapabilityMultiSelectField.test.d.ts +0 -0
- package/package.json +7 -7
- package/src/index.tsx +8 -0
- package/src/widgets/CapabilityMultiSelectField.test.tsx +143 -0
- package/src/widgets/CapabilityMultiSelectField.tsx +204 -0
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,56 @@
|
|
|
1
1
|
# @object-ui/fields
|
|
2
2
|
|
|
3
|
+
## 13.2.0
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- e492b9d: Permission sets — pure separation of **design** (Studio) and **assignment**
|
|
8
|
+
(Setup), per ADR-0056 / epic #2398. A `sys_permission_set` used to render its six
|
|
9
|
+
authorization facets in Setup as raw `[Object]` / JSON textareas, and only
|
|
10
|
+
objects+fields were editable in Studio; this reworks both surfaces.
|
|
11
|
+
|
|
12
|
+
**Setup (assign + read-only):**
|
|
13
|
+
- The six facets (`object_permissions`, `field_permissions`, `system_permissions`,
|
|
14
|
+
`row_level_security`, `tab_permissions`, `admin_scope`) now render read-only on
|
|
15
|
+
the `sys_permission_set` record page as a compact summary (counts, or capability
|
|
16
|
+
chips) plus a **“Design in Studio →”** deep-link into the structured editor
|
|
17
|
+
(`/apps/:appName/metadata/permission/:setName`, env scope). No `[Object]`, no
|
|
18
|
+
JSON — in the record view, inline edit, and the create/edit form. Implemented as
|
|
19
|
+
a `permission-facet-link` field widget stamped onto the six fields via the single
|
|
20
|
+
`ObjectStackAdapter.getObjectSchema` choke point and honored by DetailSection +
|
|
21
|
+
the record form.
|
|
22
|
+
- User assignment (add/remove via `sys_user_permission_set`) is surfaced directly
|
|
23
|
+
on the Setup record page.
|
|
24
|
+
|
|
25
|
+
**Studio (design every facet):** the permission matrix editor gains structured
|
|
26
|
+
editors for the facets that were JSON-only —
|
|
27
|
+
- **System Capabilities**: a multi-select over the live `sys_capability` registry
|
|
28
|
+
(scope-grouped, labelled chips).
|
|
29
|
+
- **Row-Level Security**: per-policy rows (object · operation · enabled) with CEL
|
|
30
|
+
USING/CHECK.
|
|
31
|
+
- **Tab Visibility**: per-tab `visible | hidden | default_on | default_off`.
|
|
32
|
+
- **Delegated Admin Scope**: business-unit + subtree, manage-assignments /
|
|
33
|
+
-bindings / author-env-sets toggles, and an assignable-permission-sets allowlist.
|
|
34
|
+
Assignment was moved out of the editor (it is now a Setup act) — the editor is
|
|
35
|
+
purely a design surface.
|
|
36
|
+
|
|
37
|
+
Storage/types are unchanged; editors read/write the draft’s existing parsed
|
|
38
|
+
fields and tolerate legacy JSON strings on load. Note: env-scope metadata saves of
|
|
39
|
+
these facets do not yet project onto the queryable `sys_permission_set` data
|
|
40
|
+
record the Setup summary reads, so a fresh Studio edit isn’t reflected in Setup’s
|
|
41
|
+
read-only view until the projection refreshes — tracked as a framework follow-up
|
|
42
|
+
(enforcement reads the authoritative metadata).
|
|
43
|
+
|
|
44
|
+
- Updated dependencies [80901aa]
|
|
45
|
+
- Updated dependencies [53c40c2]
|
|
46
|
+
- Updated dependencies [e492b9d]
|
|
47
|
+
- @object-ui/components@13.2.0
|
|
48
|
+
- @object-ui/i18n@13.2.0
|
|
49
|
+
- @object-ui/react@13.2.0
|
|
50
|
+
- @object-ui/types@13.2.0
|
|
51
|
+
- @object-ui/core@13.2.0
|
|
52
|
+
- @object-ui/providers@13.2.0
|
|
53
|
+
|
|
3
54
|
## 13.1.0
|
|
4
55
|
|
|
5
56
|
### Patch Changes
|