@nocobase/app-skills 0.1.0-beta.50 → 0.1.0-beta.51
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/package.json
CHANGED
|
@@ -271,3 +271,7 @@ Reconcile `client/pages/settings/page-permissions.ts`, the role form's catalog a
|
|
|
271
271
|
Reconcile the catalog descriptions, individual account-permission groups, category names without counts, individual action controls and labelled multi-scope summaries with the role form and locale updates. A display resource may share a stored resource ID with another display group: resolve a changed row by resource type, resource ID and action together, so later groups remain editable. Preserve all registered action IDs and existing unknown or structured policies. Update the authorization and Agent plugins together when adopting their new catalog labels, action-description metadata and administrative placement. An empty scope means no additional record access; retain default access, sharing and restriction behavior.
|
|
272
272
|
|
|
273
273
|
Keep empty-scope explanations in the range help tooltip rather than a permanent paragraph under every select. Reconcile the Tooltip primitive, scope hint label binding and localized text together; keyboard focus and touch activation must expose the same explanation without changing grants.
|
|
274
|
+
|
|
275
|
+
## Explicit Member assignments
|
|
276
|
+
|
|
277
|
+
When upgrading to the explicit Member role behavior, upgrade Authentication, Authorization, and Users together and stop old account writers before `pnpm nocobase db apply`. The Authorization seed preserves existing Member access as direct assignments before removing its global assignment; do not edit old tasks or recreate the old association. Merge the prepared user form, list, and settings translations separately. Use the new role-scope `defaultValue` only on creation, respect explicit empty arrays, and never restore Member during profile edits. Verify role removal through a direct API request and a fresh login. Recover with the database backup and matching old packages, not an inverse role assignment script.
|