@wildo-ai/framework-knowledge 1.1.1 → 1.1.3
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/dist/esm/framework-knowledge.definitions.d.ts +1 -1
- package/dist/esm/framework-knowledge.definitions.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.definitions.js +271 -8
- package/dist/esm/framework-knowledge.definitions.js.map +1 -1
- package/dist/esm/framework-knowledge.loader.d.ts +19 -0
- package/dist/esm/framework-knowledge.loader.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.loader.js +32 -0
- package/dist/esm/framework-knowledge.loader.js.map +1 -1
- package/dist/esm/framework-knowledge.schemas.d.ts +13 -2
- package/dist/esm/framework-knowledge.schemas.d.ts.map +1 -1
- package/dist/esm/framework-knowledge.schemas.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts +45 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js +55 -0
- package/dist/esm/playbooks/bottom_up.assemble-verify/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts +6 -7
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js +6 -6
- package/dist/esm/playbooks/bottom_up.build-decompose/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts +0 -4
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js +0 -2
- package/dist/esm/playbooks/bottom_up.build-dispatch/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts +0 -4
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js +0 -2
- package/dist/esm/playbooks/bottom_up.build-scale/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts +3 -9
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js +1 -3
- package/dist/esm/playbooks/bottom_up.domain-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts +10 -6
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js +25 -4
- package/dist/esm/playbooks/bottom_up.foundation/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts +1 -5
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js +1 -3
- package/dist/esm/playbooks/bottom_up.placement-plan/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts +4 -2
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js +4 -2
- package/dist/esm/playbooks/refinement.compliance-document-candidate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts +1 -2
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js +13 -14
- package/dist/esm/playbooks/refinement.document-facts/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts +3 -5
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js +3 -4
- package/dist/esm/playbooks/top_down.brand-identity/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts +2 -8
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js +0 -2
- package/dist/esm/playbooks/top_down.business-model/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts +2 -8
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js +0 -2
- package/dist/esm/playbooks/top_down.capability-map/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts +52 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js +127 -0
- package/dist/esm/playbooks/top_down.compliance-analysis/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts +75 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js +91 -0
- package/dist/esm/playbooks/top_down.compliance-conception/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts +29 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js +28 -0
- package/dist/esm/playbooks/top_down.compliance-evidence-adequacy/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts +9 -45
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js +4 -54
- package/dist/esm/playbooks/top_down.compliance-posture/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts +30 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.d.ts.map +1 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js +25 -0
- package/dist/esm/playbooks/top_down.compliance-research/playbook.definition.js.map +1 -0
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts +2 -9
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js +9 -5
- package/dist/esm/playbooks/top_down.market-analysis/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-evidence-adequacy/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts +0 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js +0 -1
- package/dist/esm/playbooks/top_down.market-research/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts +0 -9
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js +0 -2
- package/dist/esm/playbooks/top_down.market-snapshot-produce/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts +2 -8
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js +0 -2
- package/dist/esm/playbooks/top_down.phase-gate/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts +2 -8
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js +0 -2
- package/dist/esm/playbooks/top_down.requirements-definition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts +2 -8
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js +5 -4
- package/dist/esm/playbooks/top_down.scope-roadmap/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts +0 -4
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js +0 -2
- package/dist/esm/playbooks/top_down.value-proposition/playbook.definition.js.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts +4 -6
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.d.ts.map +1 -1
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js +25 -5
- package/dist/esm/playbooks/top_down.vision-elicitation/playbook.definition.js.map +1 -1
- package/dist/knowledge/manifest.json +6 -7
- package/dist/knowledge/playbooks/bottom_up.build-decompose/method.md +7 -47
- package/dist/knowledge/playbooks/bottom_up.build-decompose/playbook.json +6 -13
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/method.md +1 -82
- package/dist/knowledge/playbooks/bottom_up.build-dispatch/playbook.json +11 -6
- package/dist/knowledge/playbooks/bottom_up.build-scale/playbook.json +10 -5
- package/dist/knowledge/playbooks/bottom_up.domain-plan/playbook.json +3 -4
- package/dist/knowledge/playbooks/bottom_up.foundation/playbook.json +3 -4
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/method.md +15 -735
- package/dist/knowledge/playbooks/refinement.compliance-document-candidate/playbook.json +11 -7
- package/dist/knowledge/playbooks/refinement.document-facts/method.md +16 -123
- package/dist/knowledge/playbooks/refinement.document-facts/playbook.json +15 -8
- package/dist/knowledge/playbooks/top_down.brand-identity/playbook.json +10 -4
- package/dist/knowledge/playbooks/top_down.business-model/playbook.json +10 -4
- package/dist/knowledge/playbooks/top_down.capability-map/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.capability-map/playbook.json +12 -5
- package/dist/knowledge/playbooks/top_down.compliance-posture/playbook.json +10 -4
- package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-protocol.json +1 -1
- package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/evaluation-treatment.json +1 -1
- package/dist/knowledge/playbooks/top_down.market-analysis/method.md +165 -51
- package/dist/knowledge/playbooks/top_down.market-analysis/playbook.json +39 -21
- package/dist/knowledge/playbooks/top_down.phase-gate/playbook.json +2 -6
- package/dist/knowledge/playbooks/top_down.requirements-definition/playbook.json +10 -4
- package/dist/knowledge/playbooks/top_down.scope-roadmap/method.md +1 -1
- package/dist/knowledge/playbooks/top_down.scope-roadmap/playbook.json +11 -5
- package/dist/knowledge/playbooks/top_down.value-proposition/method.md +2 -2
- package/dist/knowledge/playbooks/top_down.value-proposition/playbook.json +11 -5
- package/dist/knowledge/playbooks/top_down.vision-elicitation/playbook.json +10 -4
- package/dist/knowledge/references/build-plan.task-graph.config.md +1 -45
- package/dist/knowledge/references/example.config.app-shell.full.md +4 -0
- package/dist/knowledge/references/example.provider.backend-module-shape.md +0 -7
- package/dist/knowledge/references/example.resource.add-resource.module-factory-map.md +1 -0
- package/dist/knowledge/references/platform.config.saas.md +0 -50
- package/dist/knowledge/references/saas.external-data.admin-endpoints.md +48 -0
- package/dist/knowledge/references/saas.frontend.app-level-component.configuration.md +10 -6
- package/dist/knowledge/references/saas.frontend.app-level-component.vocabulary.md +1 -0
- package/dist/knowledge/references/saas.frontend.resource-operation-frontend-config.md +0 -109
- package/dist/knowledge/references/saas.models.data-mode-read-list.md +0 -137
- package/dist/knowledge/references/saas.models.http-api-binding.md +29 -3
- package/dist/knowledge/references/saas.models.resource-config.builder-parameters.md +2 -4
- package/dist/knowledge/references/saas.models.resource-config.resource-configuration.md +0 -2
- package/dist/knowledge/references/saas.models.resource-config.resources-registry.md +0 -14
- package/dist/knowledge/references/saas.specifications.application-document-fact-specification.contract.md +1 -1
- package/dist/knowledge/references/saas.specifications.companion-exports.contract.md +0 -36
- package/dist/knowledge/references/zod.decorators.chainable-runtime.md +0 -26
- package/dist/knowledge/references/zod.decorators.decorator-vocabulary.md +0 -45
- package/dist/knowledge/references/zod.decorators.display-edit-modes.md +1 -1
- package/dist/knowledge/references/zod.decorators.per-primitive-ui.md +1 -1
- package/dist/knowledge/references/zod.decorators.schema-metadata.md +0 -1
- package/dist/knowledge/registries/assurance-authority-bases.json +1 -1
- package/dist/knowledge/registries/framework-topics.json +11 -48
- package/dist/knowledge/registries/playbooks.json +11 -74
- package/dist/knowledge/registries/source-tags.json +538 -622
- package/dist/knowledge/skills/INDEX.md +0 -1
- package/dist/knowledge/skills/compliance-document-authoring/SKILL.md +2 -16
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-governance.md +8 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-privacy-notice.md +74 -252
- package/dist/knowledge/skills/compliance-document-authoring/references/document-composition-service-terms.md +8 -26
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-application-document-fact-specification-contract.md +21 -36
- package/dist/knowledge/skills/compliance-document-authoring/references/framework-assurance-document-blueprint-contract.md +19 -49
- package/dist/knowledge/skills/config-app-shell/SKILL.md +8 -6
- package/dist/knowledge/skills/config-app-shell/references/framework-app-shell-api.md +11 -6
- package/dist/knowledge/skills/config-saas/references/framework-wildo-saas-config-api.md +0 -50
- package/dist/knowledge/skills/configure-billing/references/example-backend-provider-module-shape.md +0 -7
- package/dist/knowledge/skills/market-companion-prompt-enrichment/SKILL.md +0 -36
- package/dist/knowledge/skills/market-companion-prompt-enrichment/references/framework-companion-behavior-api.md +0 -36
- package/dist/knowledge/skills/module-companion-exports/references/companion-exports-by-package.md +0 -36
- package/dist/knowledge/skills/resource-add-field/references/framework-field-cross-layer-api.md +0 -109
- package/dist/knowledge/skills/resource-add-resource/SKILL.md +1 -2
- package/dist/knowledge/skills/resource-add-resource/references/framework-new-resource-core-config-api.md +2 -4
- package/dist/knowledge/skills/resource-config-wiring/SKILL.md +0 -2
- package/dist/knowledge/skills/resource-config-wiring/references/framework-saas-models-resource-config-api.md +2 -157
- package/dist/knowledge/skills/resource-custom-view/references/custom-view-contracts.md +0 -109
- package/dist/knowledge/skills/resource-external-data/SKILL.md +2 -0
- package/dist/knowledge/skills/resource-external-data/references/framework-http-api-binding-api.md +29 -3
- package/dist/knowledge/skills/resource-external-data/references/framework-pipeline-admin-endpoints-api.md +70 -0
- package/dist/knowledge/skills/resource-schema-authoring/SKILL.md +0 -1
- package/dist/knowledge/skills/resource-schema-authoring/references/decorator-layer-map.md +0 -17
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-decorator-vocabulary-api.md +0 -46
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-zod-lifecycle-and-chainable-api.md +0 -26
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-display-edit-modes-api.md +1 -1
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-frontend-resource-ui-contracts-api.md +0 -109
- package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md +1 -1
- package/dist/knowledge/skills/spec-companion-exports/references/framework-companion-exports-contract-api.md +0 -36
- package/dist/knowledge/topic-index.json +128 -285
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/dist/tsconfig.tsbuildinfo +1 -1
- package/package.json +4 -4
- package/dist/esm/.builder.pid +0 -9
- package/dist/knowledge/playbooks/bottom_up.placement-plan/method.md +0 -185
- package/dist/knowledge/playbooks/bottom_up.placement-plan/playbook.json +0 -66
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/method.md +0 -56
- package/dist/knowledge/playbooks/top_down.market-evidence-adequacy/playbook.json +0 -40
- package/dist/knowledge/playbooks/top_down.market-research/method.md +0 -68
- package/dist/knowledge/playbooks/top_down.market-research/playbook.json +0 -42
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/method.md +0 -239
- package/dist/knowledge/playbooks/top_down.market-snapshot-produce/playbook.json +0 -69
- package/dist/knowledge/references/placement-plan.config.md +0 -330
- package/dist/knowledge/references/saas.frontend.settings-hub.engine-destinations.md +0 -58
- package/dist/knowledge/references/saas.frontend.settings-hub.placement.md +0 -118
- package/dist/knowledge/references/zod.decorators.data-categories.md +0 -197
- package/dist/knowledge/rules/resource-schema-awareness.md +0 -77
- package/dist/knowledge/skills/resource-config-wiring/references/framework-personal-data-declaration-api.md +0 -622
- package/dist/knowledge/skills/resource-schema-authoring/references/framework-personal-data-category-api.md +0 -245
- package/dist/knowledge/skills/settings-placement-authoring/SKILL.md +0 -134
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-destinations-catalog.md +0 -65
- package/dist/knowledge/skills/settings-placement-authoring/references/framework-settings-placement-api.md +0 -127
- /package/dist/knowledge/playbooks/{top_down.market-snapshot-produce → top_down.market-analysis}/structured-artifact-action.json +0 -0
|
@@ -206,106 +206,6 @@ export enum ActionPlacement {
|
|
|
206
206
|
DANGER_ZONE = 'danger_zone',
|
|
207
207
|
}
|
|
208
208
|
|
|
209
|
-
/**
|
|
210
|
-
* HOW an operation's action collects its input and shows its result — the chrome the user meets
|
|
211
|
-
* when they click the button.
|
|
212
|
-
*
|
|
213
|
-
* ## Why this axis exists
|
|
214
|
-
*
|
|
215
|
-
* Until this axis, one rule decided the answer for every custom operation:
|
|
216
|
-
* *has a `requestDto` ⇒ navigate*. So an action asking for a single reason string got the same
|
|
217
|
-
* full-page treatment as a multi-step wizard, and the only way out was to author
|
|
218
|
-
* `navigationOverrides` — per operation, in terms of a zone, a transition verb and an appearance.
|
|
219
|
-
* Three concepts to answer one question.
|
|
220
|
-
*
|
|
221
|
-
* This is that one question. It is a **display-only** axis: backend authorization is untouched and
|
|
222
|
-
* `roles` remain the only security authority, exactly like its siblings {@link ActionVisibility},
|
|
223
|
-
* {@link ActionPlacement} and {@link ResourceOperationActionScope}.
|
|
224
|
-
*
|
|
225
|
-
* ## It is an ALIAS, not a parallel mechanism
|
|
226
|
-
*
|
|
227
|
-
* `MODAL` and `PAGE` do not render anything themselves — they resolve to the navigation transitions
|
|
228
|
-
* that already exist (`OVERLAY`, and the ordinary chain), so there is one runtime mechanism and one
|
|
229
|
-
* set of zone/appearance/URL semantics. `DIRECT`, `POPOVER` and `INLINE` never enter navigation at
|
|
230
|
-
* all, because none of them is a destination: nothing is pushed, no zone changes, and there is
|
|
231
|
-
* nothing for a back button to pop. `INLINE` is hosted by the collection the element belongs to —
|
|
232
|
-
* see `InPlaceOperationContext` for why that is not the navigation layer's job.
|
|
233
|
-
*
|
|
234
|
-
* Consequently an explicit `navigationOverrides` entry still WINS over a presentation authored here
|
|
235
|
-
* (it is the more specific instrument, and it is checked first in the resolution chain). Author this
|
|
236
|
-
* axis to say what KIND of chrome the action wants; author `navigationOverrides` when you need to
|
|
237
|
-
* name the zone, the appearance or the viewport yourself.
|
|
238
|
-
*
|
|
239
|
-
* ## When omitted
|
|
240
|
-
*
|
|
241
|
-
* It is DERIVED from the operation — see `resolveResourceOperationActionPresentation()`. An
|
|
242
|
-
* operation that asks for nothing executes directly; a small field set opens a modal; input the
|
|
243
|
-
* framework cannot fit in an overlay (files, nested writes, a large field set) keeps the page it
|
|
244
|
-
* has always had. An operation whose `surface` is `ADDRESSABLE` always keeps its page: the author
|
|
245
|
-
* has already said it is a deep-linkable destination.
|
|
246
|
-
*/
|
|
247
|
-
export enum ResourceOperationActionPresentation {
|
|
248
|
-
/**
|
|
249
|
-
* Execute on click, with no form at all — the confirmation dialog for a risky operation is the
|
|
250
|
-
* only thing between the click and the request.
|
|
251
|
-
*
|
|
252
|
-
* Only meaningful for an operation that needs no caller input. Declaring it on an operation that
|
|
253
|
-
* DOES have required request fields would send an empty body, so the resolver refuses to derive it
|
|
254
|
-
* there and an author who declares it anyway gets the operation's fields dropped — check
|
|
255
|
-
* `requestDto` before reaching for this.
|
|
256
|
-
*/
|
|
257
|
-
DIRECT = 'direct',
|
|
258
|
-
/**
|
|
259
|
-
* A small form anchored to the button that opened it, dismissed by clicking away.
|
|
260
|
-
*
|
|
261
|
-
* The single-input idiom ("assign to…", "snooze until…"). Transient by construction: no URL, no
|
|
262
|
-
* history entry, nothing to deep-link. Use it when the surrounding context is the point — the user
|
|
263
|
-
* is reading the row they are acting on and must not lose sight of it.
|
|
264
|
-
*/
|
|
265
|
-
POPOVER = 'popover',
|
|
266
|
-
/**
|
|
267
|
-
* The element being acted on transforms in place to collect the input, leaving its neighbours
|
|
268
|
-
* visible — the row becomes the form rather than being covered by one.
|
|
269
|
-
*
|
|
270
|
-
* Use it when the surrounding rows are the point: the user is comparing, and an overlay would hide
|
|
271
|
-
* the very thing that made them act on this row.
|
|
272
|
-
*
|
|
273
|
-
* **Transient, like {@link POPOVER}, and for the same reason.** Nothing is pushed, no URL changes,
|
|
274
|
-
* and a reload returns the list to rest. An inline row-edit is a momentary state of a listing, not
|
|
275
|
-
* a place — which is also why no admin framework deep-links one, and why anything that SHOULD be
|
|
276
|
-
* linkable, reloadable or reachable by a back button wants {@link PAGE}.
|
|
277
|
-
*
|
|
278
|
-
* **It requires a collection.** The host is provided by the list the element belongs to
|
|
279
|
-
* (`InPlaceOperationProvider`); the same action rendered on a detail page, in a danger zone or in a
|
|
280
|
-
* picker has no row to transform and degrades to an overlay rather than becoming a dead button.
|
|
281
|
-
*
|
|
282
|
-
* Note it does NOT resolve to `NavigationTransition.INPLACE`. Element-level hosting uses none of
|
|
283
|
-
* what the navigation layer offers — no zone, no stack entry, no appearance — and routing it there
|
|
284
|
-
* is exactly why that transition has never done what its own docstring promises. See
|
|
285
|
-
* `InPlaceOperationContext`.
|
|
286
|
-
*/
|
|
287
|
-
INLINE = 'inline',
|
|
288
|
-
/**
|
|
289
|
-
* An overlay above the layout — the workhorse for "a handful of fields", and the default the
|
|
290
|
-
* derivation reaches for.
|
|
291
|
-
*
|
|
292
|
-
* Resolves to {@link NavigationTransition.OVERLAY}. The concrete appearance (dialog / sheet /
|
|
293
|
-
* drawer / panel) stays the app's decision, resolved from its navigation layout exactly as any
|
|
294
|
-
* other overlay: this axis says "an overlay", not "a dialog specifically". Author
|
|
295
|
-
* `navigationOverrides` when you need to name one.
|
|
296
|
-
*/
|
|
297
|
-
MODAL = 'modal',
|
|
298
|
-
/**
|
|
299
|
-
* A routable page, resolved through the ordinary navigation chain (zone transitions, viewport
|
|
300
|
-
* overrides, the framework `PUSH` fallback) — i.e. exactly the behaviour every parameterised
|
|
301
|
-
* action had before this axis existed.
|
|
302
|
-
*
|
|
303
|
-
* The right answer for complex or multi-step input, and for anything a user should be able to
|
|
304
|
-
* link to, reload, or reach with a back button.
|
|
305
|
-
*/
|
|
306
|
-
PAGE = 'page',
|
|
307
|
-
}
|
|
308
|
-
|
|
309
209
|
/**
|
|
310
210
|
* Does an operation's action target a SINGLE resource instance, or the WHOLE
|
|
311
211
|
* collection in the current scope?
|
|
@@ -480,15 +380,6 @@ export const ResourceOperationFrontendConfigSchema = z.object({
|
|
|
480
380
|
* row id still rides the URL path too, which the handler may ignore.)
|
|
481
381
|
*/
|
|
482
382
|
rowTargetRequestField: z.string().optional(),
|
|
483
|
-
/**
|
|
484
|
-
* HOW this action collects its input — see {@link ResourceOperationActionPresentation}.
|
|
485
|
-
* Omitted derives from the operation (`resolveResourceOperationActionPresentation`): no input
|
|
486
|
-
* executes directly, a small field set opens a modal, complex input keeps its page.
|
|
487
|
-
*
|
|
488
|
-
* Display-only. An explicit `navigationOverrides` entry is the more specific instrument and wins
|
|
489
|
-
* over whatever this resolves to.
|
|
490
|
-
*/
|
|
491
|
-
actionPresentation: z.enum(ResourceOperationActionPresentation).optional(),
|
|
492
383
|
customView: z.any().optional(),
|
|
493
384
|
displayPresetOverride: z.object({
|
|
494
385
|
resourceLayoutPresetKey: z.string().optional(),
|
package/dist/knowledge/skills/resource-ui-behavior/references/framework-per-primitive-ui-api.md
CHANGED
|
@@ -20,7 +20,7 @@ Per-primitive UI parameter surfaces (string, number, enum, etc.).
|
|
|
20
20
|
*
|
|
21
21
|
* They belong to the frontend resource behavior layer, not to shared resource
|
|
22
22
|
* schemas. In application code, they are typically authored in files like:
|
|
23
|
-
* `
|
|
23
|
+
* `app/src/modules/<module>/resources/<resource>/<resource>.ui-behavior.tsx`
|
|
24
24
|
*
|
|
25
25
|
* The shared schema establishes structural meaning (`isSummaryField`,
|
|
26
26
|
* `isForeignKey`, `excludeFromUpdate`, ...). These UI parameter types control
|
|
@@ -57,7 +57,6 @@ export interface SpecificationsCompanionExports<
|
|
|
57
57
|
TRequirementsSnapshot = RequirementsSnapshot,
|
|
58
58
|
TRoadmapSnapshot = RoadmapSnapshot,
|
|
59
59
|
TBuildPlanTaskGraph = BuildPlanTaskGraph,
|
|
60
|
-
TPlacementPlan = PlacementPlan,
|
|
61
60
|
TDomainPlanOutputSet = DomainPlanOutputSet,
|
|
62
61
|
TBusinessModelLiteSnapshot = BusinessModelLiteSnapshot,
|
|
63
62
|
// Appended STRICTLY LAST (positional generics — never insert mid-list):
|
|
@@ -85,11 +84,6 @@ export interface SpecificationsCompanionExports<
|
|
|
85
84
|
// Appended STRICTLY LAST: release-process selection is a separate accepted
|
|
86
85
|
// decision, never an implicit default of routing or document necessity.
|
|
87
86
|
TDocumentReleasePolicySpecification = ApplicationDocumentReleasePolicySpecification,
|
|
88
|
-
// Appended STRICTLY LAST: WHO else processes personal data, under what legal
|
|
89
|
-
// identity and where (issue #88). Optional, and the optionality is the design:
|
|
90
|
-
// a partial register is useful and its holes are REPORTED per provider against
|
|
91
|
-
// the application's configured set, rather than blocking anything.
|
|
92
|
-
TProcessorRegister = ApplicationProcessorRegister,
|
|
93
87
|
> {
|
|
94
88
|
resourceSpecifications: TResourceSpecifications;
|
|
95
89
|
applicationBusinessSemanticsSnapshot?: TBusinessSemanticsSnapshot;
|
|
@@ -320,22 +314,6 @@ export interface SpecificationsCompanionExports<
|
|
|
320
314
|
* `validateBuildPlanTaskGraph` on the value before wiring it here.
|
|
321
315
|
*/
|
|
322
316
|
buildPlanSpecification?: TBuildPlanTaskGraph;
|
|
323
|
-
/**
|
|
324
|
-
* Application **placement** specification — WHERE every settings destination,
|
|
325
|
-
* resource operation and app view sits in the shell, and WHY (`PlacementPlan`,
|
|
326
|
-
* `_core/placement-plan/`).
|
|
327
|
-
*
|
|
328
|
-
* Produced by the `bottom_up.placement-plan` playbook as an expert-panel
|
|
329
|
-
* DELIBERATION rather than a creator elicitation: the creator does not choose
|
|
330
|
-
* placement, so each decision carries a `rationale` that answers "why is this
|
|
331
|
-
* here?" without re-running the panel. Consumed by build-decompose, which
|
|
332
|
-
* turns it into the coding tasks that author `settings-hub.config.ts` and
|
|
333
|
-
* `app-shell.config.ts`.
|
|
334
|
-
*
|
|
335
|
-
* Optional until an application reaches the bottom-up phase; app bootstraps
|
|
336
|
-
* should run `validatePlacementPlan` on the value before wiring it here.
|
|
337
|
-
*/
|
|
338
|
-
placementPlanSpecification?: TPlacementPlan;
|
|
339
317
|
/**
|
|
340
318
|
* Application **domain-plan** specification — the atomic module decomposition
|
|
341
319
|
* PLUS relationship drafts (`DomainPlanOutputSet`, `_core/domain-plan/`);
|
|
@@ -474,20 +452,6 @@ export interface SpecificationsCompanionExports<
|
|
|
474
452
|
* Omitting it is honest: unresolved document facts remain visible gaps.
|
|
475
453
|
*/
|
|
476
454
|
documentFactSpecification?: TDocumentFactSpecification;
|
|
477
|
-
/**
|
|
478
|
-
* WHO else processes this application's personal data — legal identity, processing region and the
|
|
479
|
-
* processor's own subprocessors (issue #88).
|
|
480
|
-
*
|
|
481
|
-
* A configured provider already establishes THAT a third party is involved and what function it
|
|
482
|
-
* performs. None of that is what a privacy notice's recipient statement needs, and an
|
|
483
|
-
* international-transfer statement cannot be made at all without a region.
|
|
484
|
-
*
|
|
485
|
-
* Optional, and its holes are reported rather than blocking: the companion compares this register
|
|
486
|
-
* against the application's CONFIGURED providers and names each one that is undeclared, so a partial
|
|
487
|
-
* register is useful and an empty one still produces an actionable document. An absent entry means
|
|
488
|
-
* nobody has established that processor's identity — never that the provider is unused.
|
|
489
|
-
*/
|
|
490
|
-
processorRegister?: TProcessorRegister;
|
|
491
455
|
/**
|
|
492
456
|
* Accepted application-declared semantic causality between whole
|
|
493
457
|
* specification-family states. This is not the registry's physical
|