@nocobase/app-skills 0.1.0-beta.61 → 0.1.0-beta.62
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
|
@@ -4,7 +4,7 @@ A usable application includes administration for the capabilities it uses. Do no
|
|
|
4
4
|
|
|
5
5
|
## Baseline
|
|
6
6
|
|
|
7
|
-
A newly created Default application shows Home and, for an unrestricted administrator, one System settings entry whose home page holds the protected App Foundation
|
|
7
|
+
A newly created Default application shows Home and, for an unrestricted administrator, one System settings entry whose home page holds the protected App Foundation and Database Explorer cards. Other users do not see that entry unless they are granted the Database Explorer page. It does not enable business settings or their prerequisite checks merely because plugins are installed. The template includes reusable application-owned Users and Permission management page modules, ready to enable as the application develops. Examples is already a built application and registers them. Every administration surface joins the System settings structure — one sidebar entry, a home page of cards by category, tabs inside a module — described in [System settings navigation](settings-navigation.md); follow it for every module this reference asks for.
|
|
8
8
|
|
|
9
9
|
As business capabilities are developed, automatically supply core user and permission administration and any management surfaces those capabilities need. If the core settings routes are still absent, import `systemSettingsRoutes` from `./pages/settings/routes.js` in `client/routes.ts` and append it once to the exported route contribution array after the settings shell: `const routes: readonly AppClientRouteContribution[] = [appRoutes, settingsShellRoutes, systemSettingsRoutes]`. Its routes join the shell's Accounts and permissions category through `parent: 'settingsAccount'`. Reuse an existing registration instead of duplicating it, and never register a second settings group: Users, Permission management, Workflow management and other administration modules appear as cards of the one System settings home while retaining their URLs and permission ids. Do not make the user ask for user or permission settings separately, and do not grant access to ordinary users as a side effect. Existing applications that predate these modules should install or build equivalent real management pages as part of the current development task when needed. Preserve already enabled pages and their server authorization on every iteration. Do not use a first-build flag, a one-time setup stage, or the number of development rounds as the trigger. Reuse UsersClient and AuthorizationClient; the plugins own accounts, role scopes, grants, protected sets and their invariants. Keep personal account and appearance controls in the existing account/header surfaces.
|
|
10
10
|
|