Documentation coverage

What this site documents, what it omits, and how topics map to ./ApiTables/

This site is the frontend reference for ApiTables in bolesa-app-ui. It does not replace backend API specs, OpenAPI docs, or team runbooks for control-table configuration.

In scope (frontend)

AreaDocsSource in bolesa-app-ui
Page integrationGetting started, Entry componentsReactApiTable, useTableStructure
Lifecycle & APIs (client)Architecture, Data flowController, fetcher, axiosTable
ReduxProviders, Redux storetable-providers/
Action HTTP layeruseUtilsProvideruseUtilsProvider.tsx
Columns & cellsColumns, Column typesColumnCellTypes, formatTableColumns
FiltersFiltersTableFilters, AppliedFilters
SortingSortingTableSorting, TableBody
Row actionsRow actionsRowActionsElements, TableRowActions
Bulk actionsBulk actionsTableBulkActions, ActionsOfSelection
Custom modalsCustom controls, Wired controlsApiTablesModals, custom-controls/
Global app bridgeExternal stategetExternalState, outScopeTableRefresher
UI mapUI layout, Core componentscore/, general-components/
Structure contractTable structureStructure GET + controller init
Errors & toastsErrors and feedbackerrorHandling.ts

Out of scope (document elsewhere)

TopicWhy
Backend control-table definitionsOwned by API / Laravel (or equivalent); frontend only consumes JSON
Database schema & permissionsNot in ./ApiTables/
Full list of production table namesFeature pages under app/[locale]/ choose their own load-table/... paths
WMS / other apps’ ApiTables forksThis repo targets bolesa-app-ui; other codebases may differ
Automated tests for ApiTablesNot part of this docs package

Package inventory

Every file under ./ApiTables/ in bolesa-app-ui is listed in Package map. When you add a file there, update that page and the relevant topic doc.

Before you publish

  1. Scope — Home page and index state frontend-only authorship; backend credit stays with the wider team.
  2. Custom controlsWired controls matches ApiTablesModals.tsx in bolesa-app-ui (re-check after backend adds new custom_control URLs).
  3. Dead imports — Documented unused modal imports; remove or wire before telling consumers they exist.
  4. Paths — Docs use ./ApiTables/; app imports use @/app/ApiTables/....
  5. Theme — Site defaults to dark (app/layout.tsx); content is theme-agnostic.
  6. Search — Run the docs site locally and hit ⌘K on long pages (filters, column types).
  7. Buildpnpm types:check and pnpm build should pass with no MDX errors.

Suggested reading order for new frontend developers

On this page