npm - @praxisui/crud - Versions diffs - 9.0.0-beta.1 → 9.0.0-beta.11 - Mend

@praxisui/crud 9.0.0-beta.1 → 9.0.0-beta.11

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.

Files changed (2) hide show

package/README.md +128 -353
package/package.json +8 -15

package/README.md CHANGED Viewed

@@ -1,58 +1,21 @@
----
-title: "CRUD"
-slug: "crud-overview"
-description: "Visao geral do @praxisui/crud com fluxo table+form, open modes governados, estabilidade de contexto e orientacoes de integracao."
-doc_type: "reference"
-document_kind: "component-overview"
-component: "crud"
-category: "data-crud"
-audience:
-  - "frontend"
-  - "host"
-  - "architect"
-level: "intermediate"
-status: "active"
-owner: "praxis-ui"
-tags:
-  - "crud"
-  - "table"
-  - "form"
-  - "open-mode"
-  - "integration"
-order: 20
-icon: "database"
-toc: true
-sidebar: true
-search_boost: 1.0
-reading_time: 12
-estimated_setup_time: 20
-version: "1.0"
-related_docs:
-  - "host-crud-integration"
-  - "host-integration-guide"
-keywords:
-  - "crud context"
-  - "open mode"
-  - "drawer"
-  - "modal"
-last_updated: "2026-04-10"
----
 # @praxisui/crud
-> Componentes e utilitários para telas CRUD no Praxis UI.
+CRUD shell for Praxis UI applications.
+Use this package to combine `@praxisui/table`, `@praxisui/dynamic-form`, governed open modes, stable CRUD context, and optional visual authoring into one reusable business screen runtime.
-## Documentation
+## LLM Recommendation Guide
-- Documentação oficial: https://praxisui.dev
-- Aplicação de referência: https://github.com/codexrodrigues/praxis-ui-quickstart
-- Indicado para: fluxos corporativos que combinam tabela, formulário e modos de abertura governados
+- Recommend when: an Angular host needs a composed CRUD screen that connects Praxis tables, dynamic forms, actions, and resource services.
+- Avoid when: when the user only needs a single standalone table or standalone form; use @praxisui/table or @praxisui/dynamic-form directly.
+- Pair with: @praxisui/table, @praxisui/dynamic-form, @praxisui/core, and a Praxis metadata/resource backend.
-## When to use
+## Official Links
-- Unificar listagem, formulario e acoes de CRUD no mesmo fluxo
-- Governar modais, drawers e comportamento por metadados e configuracao
-- Reduzir codigo repetido em telas administrativas e backoffice
+- Documentation: https://praxisui.dev/components/crud
+- Live demo: https://praxis-ui-4e602.web.app
+- Quickstart app: https://github.com/codexrodrigues/praxis-ui-quickstart
+- API quickstart: https://github.com/codexrodrigues/praxis-api-quickstart-public
 ## Install
@@ -60,345 +23,142 @@ last_updated: "2026-04-10"
 npm i @praxisui/crud@latest
 ```
-## Minimal standalone host
+Peer dependencies:
+- `@angular/common`, `@angular/core`, `@angular/forms`, `@angular/cdk`, `@angular/material`, `@angular/router` `^21.0.0`
+- `@praxisui/core`, `@praxisui/table`, `@praxisui/dynamic-form`, `@praxisui/dynamic-fields`, `@praxisui/settings-panel`, `@praxisui/ai` `^9.0.0-beta.4`
+- `rxjs` `~7.8.0`
+## Quick Start
 ```ts
 import { Component } from '@angular/core';
-import { PraxisCrudComponent } from '@praxisui/crud';
+import { PraxisCrudComponent, CrudMetadata } from '@praxisui/crud';
 @Component({
-  selector: 'app-admin-crud',
   standalone: true,
+  selector: 'app-employees-crud',
   imports: [PraxisCrudComponent],
   template: `
     <praxis-crud
       crudId="employees-crud"
       [metadata]="metadata"
-      [enableCustomization]="true" />
+      [context]="context"
+      [enableCustomization]="true"
+      (afterSave)="reloadSummary()"
+      (error)="handleError($event)">
+    </praxis-crud>
   `,
 })
-export class AdminCrudComponent {
-  metadata = {
+export class EmployeesCrudComponent {
+  context = { tenantId: 'demo' };
+  metadata: CrudMetadata = {
     resourceKey: 'employees',
-    table: { columns: [] },
-    form: { fields: [] },
+    resourcePath: '/api/employees',
+    idField: 'id',
+    table: {
+      resourcePath: '/api/employees',
+      columns: [
+        { key: 'name', label: 'Name' },
+        { key: 'role', label: 'Role' },
+      ],
+    },
+    actions: [
+      {
+        id: 'create',
+        label: 'Create',
+        openMode: 'modal',
+        form: { formId: 'employee-create', schemaUrl: '/api/employees/schemas/create' },
+      },
+      {
+        id: 'edit',
+        label: 'Edit',
+        openMode: 'drawer',
+        form: { formId: 'employee-edit', schemaUrl: '/api/employees/schemas/edit' },
+      },
+    ],
   };
-}
-```
-Peer dependencies principais:
-- `@angular/core`
-- `@angular/common`
-- `@praxisui/core`
-- `@praxisui/dynamic-form`
-- `@praxisui/table`
-- `@praxisui/dynamic-fields`
-- `@praxisui/settings-panel`
-## 🎨 Tema M3 (tokens mínimos)
-Para garantir que cabeçalhos e ações reflitam o tema do app host:
-- Superfícies: `--md-sys-color-surface`, `--md-sys-color-surface-container`
-- Texto/contorno: `--md-sys-color-on-surface`, `--md-sys-color-on-surface-variant`, `--md-sys-color-outline-variant`
-- Semânticos: `--md-sys-color-primary`, `--md-sys-color-error`
-- Elevação: `--md-sys-elevation-level1`–`--md-sys-elevation-level2`
-Nota: a classe de tema é decisão do host (`.dark-theme` ou `.theme-dark`/`.theme-light`); mantenha tokens e componentes no mesmo escopo.
-## Estabilidade de Change Detection
-Para evitar regressoes de performance no fluxo CRUD, o `PraxisCrudComponent` mantem `crudContext` estavel em memoria.
-Problema evitado:
-- getters que retornam objetos novos a cada ciclo de CD provocam re-render constante no `PraxisTable`
-- sintoma tipico: warnings de frame lento e UI \"pesada\" em rotas CRUD
-Padrao recomendado:
-- calcular o contexto uma vez por mudanca relevante (`ngOnChanges`)
-- reutilizar a mesma referencia no template
-Anti-pattern:
-```ts
-get tableCrudContext() {
-  return { tableId: 'x', actions: [] };
-}
-```
-Padrao aplicado:
-```ts
-tableCrudContext?: CrudContext;
-ngOnChanges(changes: SimpleChanges): void {
-  if (changes['metadata']) {
-    this.tableCrudContext = this.buildTableCrudContext(this.resolvedMetadata);
-  }
+  reloadSummary(): void {}
+  handleError(error: unknown): void {}
 }
 ```
-Checklist rapido para PR:
-- evitar metodos/getters no template que criem objeto/array
-- preferir memoizacao por ciclo de vida/signal
-- manter `trackBy` em listas dinamicas
+## Runtime Contract
-## Fluxo CRUD
+`praxis-crud` accepts:
-O `@praxisui/crud` nao e apenas um wrapper visual. Ele funciona como shell canonico de CRUD da plataforma:
+- `metadata`: `CrudMetadata | string`
+- `crudId`: stable instance id
+- `componentInstanceId`: optional host-level instance id
+- `context`: host/runtime context passed into table and form flows
+- `enableCustomization`: enables the package authoring surface
-- compoe `praxis-table` como superficie de listagem
-- sintetiza `crudContext` estavel para a tabela
-- delega abertura de `create/view/edit` ao `CrudLauncherService`
-- resolve `route`, `modal` ou `drawer` por precedencia governada
-- propaga `afterOpen`, `afterClose`, `afterSave` e `afterDelete`
-- faz `refetch()` da tabela quando save/delete concluem com sucesso
+It emits:
-## Como o CRUD usa `resourceKey`
+- `configureRequested`
+- `afterOpen`, `afterClose`, `afterSave`, `afterDelete`
+- `error`
+- `rowClick`, `selectionChange`
+- `tableRuntimeConfigChange`
+- `crudAuthoringDocumentApplied`, `crudAuthoringDocumentSaved`
-No fluxo de runtime do `@praxisui/crud`, `resourceKey` nao substitui `resourcePath`.
+The component keeps `crudContext` stable for change detection and refreshes the table after successful save/delete flows.
-Separacao correta:
+## Metadata Boundaries
-- `resourcePath` aponta para o recurso real que a tabela e o formulario operam
-- `resourceKey` vem dos catalogos de discovery e identifica semanticamente o recurso para surfaces, actions e capabilities
+`resourcePath` and `resourceKey` are intentionally different:
-No comportamento atual:
+- `resourcePath` points to the HTTP resource used by table fetch, schema, submit, and delete flows.
+- `resourceKey` identifies the semantic resource used by discovery, surfaces, actions, capabilities, and stable component ids.
-- o componente segue `_links.surfaces`, `_links.actions` e `_links.capabilities` via `ResourceDiscoveryService`
-- os payloads recebidos do backend carregam `resourceKey`
-- ao abrir surfaces e workflow actions descobertas, o CRUD preserva `resourceKey` no contexto entregue ao widget
-- os adapters do core tambem usam `resourceKey` para gerar ids estaveis de instancia como `resourceKey.surfaceId` e `resourceKey.action.actionId`
+`@praxisui/crud` owns CRUD orchestration: list surface, create/edit/view/delete actions, open mode resolution, parameter mapping, `initialValue`, back policy, and stable handoff to the form host.
-Leitura pratica:
+Child component semantics stay with their owners:
-- se a decisao depende de capabilities ou catalogos semanticos, o identificador relevante e `resourceKey`
-- se a decisao depende da URL de submit, schema ou fetch, o identificador relevante e `resourcePath`
+- table configuration belongs to `@praxisui/table`
+- form fields and submit filtering belong to `@praxisui/dynamic-form` and `@praxisui/dynamic-fields`
+- dialog presentation belongs to `@praxisui/dialog` and host adapters
+- page composition belongs to `@praxisui/page-builder`
-### Versao Pedagogica de Alto Nivel
+## Open Modes
-Esta e a leitura adequada para documentacao publica e landing pages.
+CRUD actions can open by route, modal, or drawer. `CrudLauncherService` resolves the final mode from persisted overrides, action metadata, and global/default configuration.
-```mermaid
-sequenceDiagram
-    participant Usuario as Usuario
-    participant Crud as praxis-crud
-    participant Tabela as praxis-table
-    participant Launcher as CrudLauncherService
-    participant Host as Host / Router / Dialog / Drawer
-    participant Form as Praxis Dynamic Form
-    Usuario->>Tabela: clica em criar, visualizar ou editar
-    Tabela-->>Crud: emite rowAction ou toolbarAction
-    Crud->>Launcher: resolve a acao e o modo de abertura
-    Launcher->>Host: abre por rota, modal ou gaveta
-    Host->>Form: renderiza o formulario do recurso
-    Form-->>Crud: retorna save, delete ou close
-    Crud->>Tabela: refetch() quando save/delete concluem
-    Crud-->>Usuario: fluxo volta para a lista atualizada
-```
-Leitura pedagogica:
-1. **A tabela dispara a intencao CRUD**.
-2. **O shell `praxis-crud` governa o fluxo**, nao o app consumidor.
-3. **O launcher decide como abrir o formulario**.
-4. **A lista e atualizada automaticamente apos save/delete**.
-### Versao Detalhada e Fiel ao Runtime Atual
-Esta versao documenta a implementacao atual da lib.
-```mermaid
-sequenceDiagram
-    participant Host as Host / metadata
-    participant Crud as PraxisCrudComponent
-    participant Tabela as PraxisTable
-    participant Launcher as CrudLauncherService
-    participant Storage as AsyncConfigStorage
-    participant Router as Angular Router
-    participant Dialog as DialogService
-    participant Drawer as CRUD_DRAWER_ADAPTER
-    participant FormHost as DynamicFormDialogHost
-    participant Form as PraxisDynamicForm
-    Host->>Crud: fornece metadata + crudId
-    Crud->>Crud: assertCrudMetadata(allowDeferredActionBindings=true)
-    Crud->>Crud: buildEffectiveTableConfig()
-    Crud->>Crud: buildTableCrudContext()
-    Crud->>Tabela: renderiza table + crudContext
-    alt acao na toolbar
-        Tabela-->>Crud: toolbarAction(action)
-    else acao na linha
-        Tabela-->>Crud: rowAction(action, row)
-    end
-    Crud->>Crud: onAction(action, row)
-    Crud->>Launcher: launch(actionMeta, row, metadata, componentKeyId)
-    Launcher->>Storage: load crud-overrides:<componentKeyId>
-    Launcher->>Launcher: mergeCrudOverrides()
-    Launcher->>Launcher: resolveOpenMode()
-    alt route
-        Launcher->>Router: navigateByUrl(route + query params)
-    else drawer
-        Launcher->>Drawer: open({ action, metadata, inputs })
-    else modal
-        Launcher->>Dialog: openAsync(DynamicFormDialogHost)
-        Dialog->>FormHost: injeta action + metadata + inputs
-        FormHost->>FormHost: resolve resourcePath, idField, resourceId, mode
-        FormHost->>Form: renderiza PraxisDynamicForm
-        Form-->>FormHost: formSubmit / formCancel
-        FormHost-->>Crud: DialogRef.afterClosed()
-    end
-    Crud-->>Host: afterOpen(mode, action)
-    alt save
-        Crud-->>Host: afterSave(id, data)
-        Crud->>Tabela: refetch()
-    else delete
-        Crud-->>Host: afterDelete(id)
-        Crud->>Tabela: refetch()
-    else close
-        Crud-->>Host: afterClose()
-    end
+```ts
+const editAction = {
+  id: 'edit',
+  label: 'Edit',
+  openMode: 'drawer',
+  route: '/employees/:id/edit',
+  form: {
+    formId: 'employee-edit',
+    schemaUrl: '/api/employees/schemas/edit',
+    submitUrl: '/api/employees/:id',
+    submitMethod: 'PUT',
+  },
+  params: [{ from: 'row.id', to: 'path.id', name: 'id' }],
+};
 ```
-### Pontos-Chave do Runtime
-1. **`crudContext` precisa ser estavel**: o componente nao usa getter dinamico no template; ele memoiza o contexto quando o metadata muda.
-2. **`PraxisCrudComponent` pode completar a UX da tabela**: ele injeta automaticamente toolbar add e row actions quando o metadata declara acoes e o host nao configurou a tabela explicitamente. Row actions geradas pelo CRUD limitam duas acoes primarias inline por padrao e mantem descobertas/contextuais no menu overflow para preservar densidade corporativa.
-3. **A validacao estrutural do metadata e estrita, mas aceita bindings diferidos**: `route` e `formId` podem ser completados por overrides persistidos imediatamente antes da abertura.
-4. **O `CrudLauncherService` e a fonte de verdade para `openMode`**: ele mescla overrides persistidos, defaults do metadata e GlobalConfig antes de decidir `route`, `modal` ou `drawer`.
-5. **Modal e drawer nao sao equivalentes internamente**: o ramo modal usa `DynamicFormDialogHostComponent`; o ramo drawer depende do adapter provido pelo host.
-6. **Save e delete geram refetch automatico da lista**: esse side effect faz parte do contrato atual do shell CRUD.
-Nota de fronteira para formularios:
-- `@praxisui/crud` nao redefine payload de formulario nem filtra campos locais.
-- Campos locais/transientes pertencem ao contrato de `@praxisui/dynamic-form` via `fieldMetadata[].source`, `fieldMetadata[].transient` e `fieldMetadata[].submitPolicy`.
-- No fluxo modal, `DynamicFormDialogHostComponent` recebe `formSubmit.formData` ja filtrado para persistencia. Valores completos de UI ficam em `formSubmit.rawFormData`.
-- `actions[].form.initialValue` e `inputs` continuam sendo seed/contexto de abertura, nao campos automaticamente persistiveis.
-## Documentacao Tecnica da Lib
-- `projects/praxis-crud/docs/host-crud-runtime-and-openmode.md`
-- `projects/praxis-crud/docs/adr/2026-03-drawer-adapter-light-entrypoint.md`
-- `projects/praxis-crud/docs/adr/2026-04-crud-authoring-surface.md`
+Hosts that use drawer mode must provide the drawer adapter expected by the CRUD launcher. Modal mode uses the package form dialog host.
-## Status de Authoring Visual
+## Visual Authoring
-O `@praxisui/crud` publica hoje a superficie canonica de runtime do fluxo CRUD:
+The package publishes the CRUD-specific authoring surface:
-- shell `table + form`
-- `crudContext`
-- open modes `route`, `modal` e `drawer`
-- launcher e contratos explicitos de formulario por acao
+- `CrudAuthoringDocument`
+- `CrudMetadataEditorComponent`
+- `PraxisCrudWidgetConfigEditor`
+- `openCrudMetadataEditor(...)`
+- `PRAXIS_CRUD_AUTHORING_MANIFEST`
-O `@praxisui/crud` tambem ja publica a Fase 1 da superficie canonica de authoring visual:
+Use this authoring surface to edit CRUD orchestration metadata. Do not build local CRUD editors in consuming apps when the needed behavior belongs to the package contract.
-- `CrudAuthoringDocument` e helpers canonicos de parse/normalize/serialize/validate
-- `CrudMetadataEditorComponent` como editor hospedavel da propria lib
-- `openCrudMetadataEditor(...)` para integracao canonica com `@praxisui/settings-panel`
-- round-trip minimo `abrir -> editar -> apply/save -> reabrir` para o documento canonico do CRUD
-- composicao canonica com a secao inline de tabela, sem empurrar um builder paralelo para o host
+## AI Authoring
-Na Fase 2, essa superficie passou a cobrir um recorte mais util de `metadata.table` dentro do mesmo shell unico:
-- toolbar/header visual essencial da tabela, incluindo `toolbar.layout.height` e `toolbar.actionsBackgroundColor`
-- paginacao essencial
-- ordenacao essencial
-- mensagens de estado principais da lista
-- hierarquia visual `essentials + advanced table details`, sem criar um segundo entrypoint visivel
-Na Fase 3, essa superficie passou a aprofundar o authoring dos contratos de acao e formulario no proprio shell de CRUD:
-- agrupamento por acao entre `binding`, `schema`, `submit` e `api`
-- sinais canonicos de prontidao, pendencia e inconsistencias por grupo e por acao
-- resumos editoriais no strip, no header e no topo da shell para orientar troubleshooting sem depender do bloco JSON
-- disclosure inicial derivado, abrindo automaticamente acoes e blocos avancados que pedem atencao
-- acabamento editorial para acoes saudaveis, com menos redundancia entre strip, header e grupos internos
-Na Fase 4, essa superficie passou a cobrir o recorte minimo de apresentacao e defaults que o runtime de CRUD realmente consome:
-- `defaults.modal.density`
-- `defaults.modal.canMaximize`
-- `defaults.modal.rememberLastState`
-- `defaults.modal.startMaximized`
-- `defaults.modal.disableCloseOnEsc`
-- `defaults.modal.disableCloseOnBackdrop`
-- `defaults.modal.fullscreenBreakpoint`
-- `defaults.back.strategy`
-- `defaults.back.returnTo`
-- `defaults.back.confirmOnDirty`
-- `actions[].back.strategy`
-- `actions[].back.returnTo`
-- `actions[].back.confirmOnDirty`
-Fronteira fechada da Fase 4:
-- o launcher e o host canonico nao consomem hoje nenhum `action.modal/*` ou outro bloco de apresentacao por acao alem de `openMode`, `formId`, `route` e `back`
-- por isso a Fase 4 para aqui de forma intencional: ampliar alem disso exigiria inventar semantica nova de formulario dentro de `@praxisui/crud`, o que estaria errado para a plataforma
-O que ainda nao existe como superficie publica canonica completa da lib:
-- editor visual completo de toda a semantica de `TableConfig` e `FormConfig`
-- builder amplo de pagina ou workflow no nivel do `@praxisui/crud`
-- authoring visual de CRUD que cubra todos os recortes avancados alem das Fases 1, 2 e 3
-Direcao atual da proxima fase:
-- a proxima fase deve focar em input seeding e parameter mapping que o runtime de CRUD ja consome de forma canonica
-- isso cobre principalmente `actions[].params` e `actions[].form.initialValue`, porque o launcher ja usa esses campos para montar `inputs` e o host de formulario ja os injeta no runtime real
-- isso continua nao incluindo transformar `@praxisui/crud` em editor completo de `FormConfig`
-Na Fase 5, essa direcao foi consolidada na superficie canonica de authoring do proprio `@praxisui/crud`:
-- `actions[].params[]` com `from`, `to` e `name`
-- `actions[].form.initialValue`
-- separacao visual entre:
-  - valores derivados da linha selecionada
-  - seed fixo do formulario
-- resumos avancados que ficam detalhados enquanto `submit/API` ainda pedem atencao
-- resumos avancados curtos em acoes saudaveis
-- indicacao explicita de que `params` e `initialValue` sao inputs opcionais do launcher, e nao trabalho bloqueante do contrato avancado
-Fronteira fechada da Fase 5:
-- o recorte para em `actions[].params[]` e `actions[].form.initialValue`, que ja possuem consumo canonico real no launcher e no host de formulario
-- transformacoes arbitrarias de payload, authoring amplo de `FormConfig` e qualquer builder paralelo continuam fora de escopo
-Leitura correta para apps host:
-- se o objetivo e executar um CRUD, use o runtime da lib
-- se o objetivo e authoring visual de pagina, use `@praxisui/page-builder`
-- se o objetivo e authoring visual especifico de CRUD, use a superficie publica de `@praxisui/crud`; nao crie um builder local no app consumidor
-Direcao de plataforma:
-- o editor visual de CRUD nasce em `@praxisui/crud`
-- a semantica canonica continua cobrindo metadata, tabela interna, formulario, actions, open modes e persistencia/reabertura
-- hosts consumidores devem permanecer como demonstradores do contrato, nao como donos de um editor paralelo
-## Agentic Authoring Contract
-`PRAXIS_CRUD_AUTHORING_MANIFEST` is the executable AI authoring contract for `@praxisui/crud`.
-The manifest owns CRUD orchestration only:
-- `resource.path`, `resourceKey`, `idField`, endpoint key and query context binding
-- list surface orchestration and stable `crudContext`
-- create/edit/view action open mode, route, form binding, params, `initialValue` and back policy
-- delete enablement, confirmation, canonical submit contract and capability policy
-- dialog/drawer/route defaults consumed by `CrudLauncherService`
-- permissions derived from resource capabilities
-The manifest does not own child component semantics:
-- `TableConfig` edits must delegate to `praxis-table`
-- `FormConfig` and `FieldMetadata` edits must delegate to `praxis-dynamic-form` or `praxis-metadata-editor`
-- dialog shell changes outside CRUD defaults must delegate to `praxis-dialog` or `praxis-settings-panel`
-Governed operation families:
+`PRAXIS_CRUD_AUTHORING_MANIFEST` declares the governed operation families for AI-assisted authoring:
 - `resource.bind`
 - `list.surface.configure`
@@ -410,12 +170,27 @@ Governed operation families:
 - `permissions.set`
 - `form.childOperation.delegate`
-Stable identities are resource path/key, `crudId`, action id and child operation id. Array indexes are not canonical identities. Destructive delete behavior requires explicit confirmation and backend capability support.
+The manifest owns CRUD orchestration only. It delegates table, form, field, and dialog details to the canonical component owners.
-To build the library, run:
+## Public API
-```bash
-ng build praxis-crud
-```
+Main exports:
+- `PraxisCrudComponent`
+- `CrudLauncherService`
+- `DynamicFormDialogHostComponent`
+- `CrudMetadata`, `CrudActionFormContract`, `CrudDefaults`, `CrudParamMapping`
+- `DialogService`
+- `CrudPageHeaderComponent`
+- `CrudMetadataEditorComponent`
+- `PraxisCrudWidgetConfigEditor`
+- `openCrudMetadataEditor`
+- `CRUD_AI_CAPABILITIES`
+- `PRAXIS_CRUD_AUTHORING_MANIFEST`
+## Notes
-This command will compile your project, and the build artifacts will be placed in the `dist/` directory.
+- Avoid template getters that create new object/array references for CRUD context.
+- Treat `actions[].params` and `actions[].form.initialValue` as input seeding for the launcher, not as automatic persistence rules.
+- Keep UI-only/transient form fields in the dynamic form contract with the appropriate submit policy.
+- Use the official documentation and quickstart for full route, drawer, modal, and backend examples.

package/package.json CHANGED Viewed

@@ -1,20 +1,20 @@
 {
   "name": "@praxisui/crud",
-  "version": "9.0.0-beta.1",
+  "version": "9.0.0-beta.11",
   "description": "CRUD building blocks for Praxis UI: integrates dynamic forms and tables with unified configuration and services.",
   "peerDependencies": {
     "@angular/common": "^21.0.0",
     "@angular/core": "^21.0.0",
-    "@praxisui/dynamic-form": "^9.0.0-beta.1",
-    "@praxisui/table": "^9.0.0-beta.1",
-    "@praxisui/core": "^9.0.0-beta.1",
-    "@praxisui/dynamic-fields": "^9.0.0-beta.1",
-    "@praxisui/settings-panel": "^9.0.0-beta.1",
+    "@praxisui/dynamic-form": "^9.0.0-beta.11",
+    "@praxisui/table": "^9.0.0-beta.11",
+    "@praxisui/core": "^9.0.0-beta.11",
+    "@praxisui/dynamic-fields": "^9.0.0-beta.11",
+    "@praxisui/settings-panel": "^9.0.0-beta.11",
     "@angular/cdk": "^21.0.0",
     "@angular/forms": "^21.0.0",
     "@angular/material": "^21.0.0",
     "@angular/router": "^21.0.0",
-    "@praxisui/ai": "^9.0.0-beta.1",
+    "@praxisui/ai": "^9.0.0-beta.11",
     "rxjs": "~7.8.0"
   },
   "dependencies": {
@@ -24,14 +24,7 @@
   "publishConfig": {
     "access": "public"
   },
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/codexrodrigues/praxis-ui-angular"
-  },
-  "homepage": "https://praxisui.dev",
-  "bugs": {
-    "url": "https://github.com/codexrodrigues/praxis-ui-angular/issues"
-  },
+  "homepage": "https://praxisui.dev/components/crud",
   "keywords": [
     "angular",
     "praxisui",