@praxisui/visual-builder 9.0.0-beta.9 → 9.0.0-beta.90
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 +6 -27
- package/ai/component-registry.json +1911 -0
- package/fesm2022/praxisui-visual-builder.mjs +652 -571
- package/package.json +10 -6
- package/types/praxisui-visual-builder.d.ts +13 -5
package/README.md
CHANGED
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
# @praxisui/visual-builder
|
|
2
2
|
|
|
3
|
-
Visual rule builder for Praxis UI with JSON Logic as the canonical contract,
|
|
3
|
+
Visual rule builder for Praxis UI with JSON Logic as the canonical contract, a governed context-variable registry and visual/manual authoring for the supported runtime subset.
|
|
4
4
|
|
|
5
5
|
## LLM Recommendation Guide
|
|
6
6
|
|
|
7
|
-
- Recommend when: users need a visual rule/expression builder for JSON Logic-style conditions, validation,
|
|
7
|
+
- Recommend when: users need a visual rule/expression builder for JSON Logic-style field conditions, validation, field-to-field comparisons, and governed Praxis authoring flows.
|
|
8
8
|
- Avoid when: as a replacement for domain rule execution or backend policy enforcement.
|
|
9
9
|
- Pair with: @praxisui/core, @praxisui/table-rule-builder, @praxisui/dynamic-form, and backend validation contracts.
|
|
10
10
|
|
|
@@ -18,13 +18,13 @@ Visual rule builder for Praxis UI with JSON Logic as the canonical contract, con
|
|
|
18
18
|
|
|
19
19
|
- Build visual rule editors over the same JSON Logic contract used by Praxis runtimes
|
|
20
20
|
- Validate and review rules without inventing a second canonical syntax
|
|
21
|
-
-
|
|
21
|
+
- Register scoped contextual variables for contextual/template flows without advertising them as visual field-condition operands
|
|
22
22
|
|
|
23
23
|
## Features
|
|
24
24
|
|
|
25
25
|
- `RuleEditorComponent`: canonical visual editor for target, condition and effect authoring
|
|
26
|
-
- `ContextVariableManagerComponent`: contextual variable management for builder-driven flows
|
|
27
26
|
- `RuleBuilderService`: canonical state and conversion flow for visual authoring and JSON Logic output
|
|
27
|
+
- `ContextManagementService`: scoped context variable registry for builder-driven flows
|
|
28
28
|
- JSON Logic authoring: visual and manual JSON editing over the canonical runtime contract, without textual DSL fallback
|
|
29
29
|
- Governed authoring: one persisted structure across builder, AI and runtime
|
|
30
30
|
|
|
@@ -36,28 +36,6 @@ npm install @praxisui/visual-builder@latest
|
|
|
36
36
|
|
|
37
37
|
## Quick Start
|
|
38
38
|
|
|
39
|
-
### Context Variable Management
|
|
40
|
-
|
|
41
|
-
```typescript
|
|
42
|
-
import { Component } from '@angular/core';
|
|
43
|
-
import { ContextVariableManagerComponent } from '@praxisui/visual-builder';
|
|
44
|
-
|
|
45
|
-
@Component({
|
|
46
|
-
standalone: true,
|
|
47
|
-
imports: [ContextVariableManagerComponent],
|
|
48
|
-
template: `
|
|
49
|
-
<praxis-context-variable-manager
|
|
50
|
-
[(contextVariables)]="contextVariables"
|
|
51
|
-
[allowedScopes]="allowedScopes">
|
|
52
|
-
</praxis-context-variable-manager>
|
|
53
|
-
`,
|
|
54
|
-
})
|
|
55
|
-
export class VariableManagementComponent {
|
|
56
|
-
contextVariables = [];
|
|
57
|
-
allowedScopes = ['user', 'session', 'global'];
|
|
58
|
-
}
|
|
59
|
-
```
|
|
60
|
-
|
|
61
39
|
### Visual Rule Editor
|
|
62
40
|
|
|
63
41
|
```typescript
|
|
@@ -127,7 +105,7 @@ Use the canonical public services:
|
|
|
127
105
|
Main exports available from `@praxisui/visual-builder`:
|
|
128
106
|
|
|
129
107
|
- Agentic authoring: `PRAXIS_VISUAL_BUILDER_AUTHORING_MANIFEST`
|
|
130
|
-
- Components: `RuleEditorComponent`, `RuleCanvasComponent`, `RuleNodeComponent`, `FieldConditionEditorComponent`, `ConditionalValidatorEditorComponent`, `CollectionValidatorEditorComponent`, `MetadataEditorComponent`, `JsonViewerComponent`, `ExportDialogComponent`, `VisualRuleBuilderComponent`, `TemplateGalleryComponent`, `TemplateEditorDialogComponent`, `TemplatePreviewDialogComponent`, `RuleListComponent
|
|
108
|
+
- Components: `RuleEditorComponent`, `RuleCanvasComponent`, `RuleNodeComponent`, `FieldConditionEditorComponent`, `ConditionalValidatorEditorComponent`, `CollectionValidatorEditorComponent`, `MetadataEditorComponent`, `JsonViewerComponent`, `ExportDialogComponent`, `VisualRuleBuilderComponent`, `TemplateGalleryComponent`, `TemplateEditorDialogComponent`, `TemplatePreviewDialogComponent`, `RuleListComponent`
|
|
131
109
|
- Services: `RuleBuilderService`, `ExportIntegrationService`, `WebhookIntegrationService`, `RuleTemplateService`, `RuleValidationService`, `RuleNodeRegistryService`, `ContextManagementService`, `FieldSchemaService`
|
|
132
110
|
- Models/Types: `FieldSchema`, `RuleBuilderConfig`, `VisualBuilderMode`, `ArrayFieldSchema`, `ContextScope`, `ContextEntry`, `ContextValue`
|
|
133
111
|
|
|
@@ -156,6 +134,7 @@ Boundary rules:
|
|
|
156
134
|
- conditions persist as JSON Logic objects, not JavaScript or legacy textual DSL
|
|
157
135
|
- effects must be constrained by target property schemas and `RULE_PROPERTY_SCHEMA`
|
|
158
136
|
- `dsl.roundTrip.validate` validates the JSON export/import path currently implemented by `RuleBuilderService`; form-config import remains supported but is not advertised as a round-trip export target by this operation
|
|
137
|
+
- field-to-field comparisons are part of the supported visual subset; context-variable and function-result operands in field conditions remain planned until a canonical JSON Logic shape exists
|
|
159
138
|
- component-specific configuration belongs to child component manifests
|
|
160
139
|
|
|
161
140
|
## Legacy Note
|