@praxisui/dynamic-fields 3.0.0-beta.7 → 3.0.0-beta.8
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 +17 -0
- package/fesm2022/praxisui-dynamic-fields.mjs +31163 -30685
- package/fesm2022/praxisui-dynamic-fields.mjs.map +1 -1
- package/index.d.ts +27 -8
- package/package.json +5 -5
package/README.md
CHANGED
|
@@ -164,6 +164,23 @@ const isRegistered = registry.isRegistered(FieldControlType.INPUT);
|
|
|
164
164
|
- `projects/praxis-dynamic-fields/docs/dynamic-fields-inline-components-guide.md` (slug: `dynamic-fields-inline-components-guide`)
|
|
165
165
|
- `projects/praxis-dynamic-fields/docs/generic-crud-service.md`
|
|
166
166
|
|
|
167
|
+
## Editorial governance
|
|
168
|
+
|
|
169
|
+
Para fields mantidos pela propria lib, a semantica editorial canonica nasce em `src/lib/editorial/**`.
|
|
170
|
+
|
|
171
|
+
Fronteira oficial:
|
|
172
|
+
|
|
173
|
+
- `ComponentMetadataEditorialDescriptor`: fonte canonica de `friendlyName`, `description`, `tooltip`, `icon`, bindings e i18n para familias governadas.
|
|
174
|
+
- `ComponentDocMeta`: artefato derivado para builders, discovery e compatibilidade de runtime; nao deve redefinir copy editorial da mesma familia governada.
|
|
175
|
+
- `dynamic-fields-playground.catalog.ts`: camada derivada para showcase/discovery; pode adicionar `recommendedWhen`, `avoidWhen`, estados e snippets, mas nao deve reinventar copy canonica.
|
|
176
|
+
- `@praxisui/dynamic-form`: consumidor; resolve nome/icone/descricao via `ComponentMetadataRegistry.resolveEditorial(..., { namespace: 'dynamicFields' })`.
|
|
177
|
+
|
|
178
|
+
Estado atual da trilha:
|
|
179
|
+
|
|
180
|
+
- a governanca editorial canonica cobre a wave 1 registrada em `dynamic-fields-wave-1.registry.ts`;
|
|
181
|
+
- familias fora da wave 1 ainda podem expor `ComponentDocMeta` proprio, mas isso nao as transforma em nova fonte canonica;
|
|
182
|
+
- ao promover uma nova familia para a trilha canonica, a ordem correta e: descriptor editorial -> metadata derivado -> catalogo derivado -> consumo no `dynamic-form`.
|
|
183
|
+
|
|
167
184
|
### Componentes Suportados
|
|
168
185
|
|
|
169
186
|
A fonte de verdade do suporte default e o `ComponentRegistryService`.
|