ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
439248ba15
TenantAtlas/specs/057-filament-v5-upgrade/contracts/README.md
ahmido 971105daa9 057-filament-v5-upgrade (#66) 
Summary: Upgrade Filament to v5 (Livewire v4), replace Filament v4-only plugins, add first-party JSON renderer, and harden Monitoring/Ops UX guardrails.
What I changed:
Composer: upgraded filament/filament → v5, removed pepperfm/filament-json and lara-zeus/torch-filament, added torchlight/engine.
Views: replaced JSON viewer with json-viewer.blade.php and updated snapshot display.
Tests: added DB-only + tenant-isolation guard tests under Monitoring and OpsUx, plus Filament smoke tests.
Specs: added/updated specs/057-filament-v5-upgrade/* (spec, tasks, plan, quickstart, research).
Formatting: ran Pint; ran full test suite (641 passed, 5 skipped).
Validation:
Ran ./vendor/bin/sail artisan test (full suite) — all tests passed.
Ran ./vendor/bin/sail pint --dirty — formatting applied.
Ran npm run build locally (Vite) — assets generated.
Notes / Rollback:
Rollback: revert composer.json/composer.lock and build assets; documented in quickstart.md.
One pending app migration was noted during validation; ensure migrations are applied in staging before deploy.
Reviewers: @frontend, @backend (adjust as needed)
Spec links:
spec.md
tasks.md
quickstart.md

Co-authored-by: Ahmed Darrazi <ahmeddarrazi@adsmac.local>
Reviewed-on: #66
2026-01-20 21:19:27 +00:00

664 B
Raw Blame History

Contracts (API / Graph)

This feature is a UI framework upgrade (Filament v5 + Livewire v4).

External HTTP / API Contracts

  • No new application API endpoints are introduced.
  • No OpenAPI / GraphQL contract changes are required.

Microsoft Graph

  • No new Microsoft Graph calls or behaviors are introduced.
  • Any existing Graph usage remains behind GraphClientInterface and the contract registry in config/graph_contracts.php.

Monitoring DB-only Guardrail

  • Monitoring → Operations UI (including widgets/partials/tabs) remains DB-only during render and background Livewire requests.
  • “Remote call” is defined as any outbound HTTP request.