@praxisui/ai

PraxisAi

This project was generated using Angular CLI version 20.3.0.

Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

ng generate component component-name

For a complete list of available schematics (such as components, directives, or pipes), run:

ng generate --help

Building

To build the library, run:

ng build praxis-ai

This command will compile your project, and the build artifacts will be placed in the dist/ directory.

Publishing the Library

Once the project is built, you can publish your library by following these steps:

• Navigate to the dist directory:

  cd dist/praxis-ai
  

• Run the npm publish command to publish your library to the npm registry:

  npm publish
  

Running unit tests

To execute unit tests with the Karma test runner, use the following command:

ng test

Running end-to-end tests

For end-to-end (e2e) testing, run:

ng e2e

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.

Backend AI endpoints (Praxis Config)

The UI uses the backend orchestration endpoints instead of calling providers directly.

Provider catalog and validation

• GET /api/praxis/config/ai/providers/catalog
• POST /api/praxis/config/ai/providers/models
• POST /api/praxis/config/ai/providers/test

models/test accept { provider, apiKey?, model? }. When apiKey is omitted, the backend uses the encrypted key stored in global config.

Suggestions (deterministic)

• POST /api/praxis/config/ai/suggestions

Example payload:

{
  "componentId": "praxis-table",
  "componentType": "table",
  "currentState": {
    "config": { "columns": [] },
    "capabilities": [],
    "runtimeState": { "rowsTotal": 120 }
  },
  "dataProfile": { "rowCount": 120 },
  "maxSuggestions": 5,
  "locale": "pt-BR"
}

Patch generation

• POST /api/praxis/config/ai/patch

Payload:

{
  "componentId": "praxis-table",
  "componentType": "table",
  "userPrompt": "Habilitar paginacao com 10 itens por pagina",
  "currentState": { "columns": [] },
  "dataProfile": { "rowCount": 120, "columns": { "status": { "inferredType": "string", "cardinality": 3 } } },
  "schemaFields": [{ "name": "status", "type": "string", "options": ["Ativo", "Inativo"] }],
  "runtimeState": { "rowsTotal": 120, "pageIndex": 0 }
}

Notes:

• currentState must be the config root (not wrapped under config).
• Clarifications may return { type: "clarification", message, options }.

Assistant local history (UI)

The assistant stores a lightweight local history in the browser using localStorage. It is scoped by { tenantId, env, userId } derived from the same headers used by the API (X-Tenant-ID, X-Env, X-User-ID).

Storage keys:

• praxis.ai.history.index:{tenantId}:{env}:{userId}
• praxis.ai.history.session:{sessionId}

Retention:

• Sessions older than 30 days are removed on read.
• Only user prompts and short assistant summaries are stored (no full config payloads or diffs).
• Sensitive tokens/credentials are redacted before persistence.

Assistant risk policy (tenant-aware)

The assistant supports a risk confirmation policy resolved per tenant from global config:

• ai.riskPolicy = "strict" (default): medium/high risk requires explicit confirmation (fail-safe).
• ai.riskPolicy = "standard": explicit backend requiresConfirmation=false is respected.

You can also override this at component level using @Input() riskPolicy.

For enterprise safety, manual patch reapply flows (JSON/path editor) are also confirmation-gated and follow the same resolved risk policy.

The manual patch editor UI is disabled by default and can be enabled explicitly with @Input() allowManualPatchEdit = true.

Assistant UX surfaces (Material 3 host-aware)

• The assistant task flow uses a descriptive 4-step timeline (Pedido, Proposta, Impacto, Aplicação).
• Clarification options are rendered as decision cards with metadata labels.
• Review/clarification modes render a "thought + plan" summary card.
• All premium styling remains bound to Material 3 host tokens (no independent dark theme inside the lib).