cs transaction web

Experience · Frontend · Active

cs transaction web

React and Vite frontend for CS Transaction Manage, rendering the ledger workspace, onboarding, agenda, transactions, series and investments through same-origin APIs.

• React 19
• Vite
• Redux Toolkit
• react-intl
• Recharts
• Tailwind 4

Spec sheet

Repository path

cs-transacion-manage/apps/web

Runtime

React 19 + Vite

Public host

http://transactions.cs.lvh.me:8080

Frontend rule

Same-origin /api only

Responsibilities

• Render the transaction-management product UI.
• Consume only the local BFF through /api.
• Use access.capabilities from auth responses to hide unavailable navigation, actions and routes.
• Use the local shared package for API-facing types.
• Route local dev API calls through the Vite proxy configured by VITE_API_PROXY_TARGET.

Interfaces and contract surface

• GET / via transactions host
• Same-origin /api
• Vite dev server on 5179

Consumers

• Internal users via browser

Dependencies and external touchpoints

• cs transaction api
• cs transaction shared

Notes

• The frontend has no direct Core-service calls; capability checks are UX-only and backend guards remain authoritative.

Source references

• cs-transacion-manage/apps/web/package.json
• cs-transacion-manage/apps/web/vite.config.ts
• cs-transacion-manage/apps/web/src

Capability UI

Il frontend riceve access da /api/auth/me e usa access.capabilities per filtrare navigazione, azioni e route. Questo filtro e solo UX: la sicurezza resta nei guard del BFF.

Nel dettaglio /setup/users/:id, un admin vede il pannello capability utente. Il pannello legge e salva solo tramite /api/users/:id/capabilities; non chiama direttamente platform-auth-service.