Context
softwarecatalog is on the Tier-4 CnAppRoot shell with @conduction/nextcloud-vue@^1.0.0-beta.40 (these landed in #226), so its six type:"index" pages (Contactpersonen, Contracten, Standaarden, Reviews, Komplianties, Moduleversies) now self-fetch and render rows. The column values are raw — no formatter / widget / aggregate wired yet.
Ask
- Add
src/services/formatters.js (procest is the reference) and pass it as :formatters to CnAppRoot in App.vue. Prefer widget:"badge" (built in) for status columns.
- Wire status/enum columns:
Contracten — status column → widget:"badge"Standaarden — status (and categorie?) → widget:"badge" / formatterKomplianties (compliance) — its status field → widget:"badge"- any date columns →
formatter (or wait for the built-in date formatter — nextcloud-vue#224)
- Consider an
aggregate column where useful — e.g. a Standaard's "N implementations" or an Organisatie's contactpersonen count (note Organisaties is currently type:"custom"; converting it to type:"index" + config.cardComponent:"OrganisatieCard" is tracked separately — the OrganisationModal/AddContactpersoonModal/status-dialog flow around it is what keeps it custom for now).
Part of the fleet manifest-index wave (pipelinq #351, procest #436, scholiq #71). Non-production → auto-merge OK once CI is green.
Context
softwarecatalog is on the Tier-4
CnAppRootshell with@conduction/nextcloud-vue@^1.0.0-beta.40(these landed in #226), so its sixtype:"index"pages (Contactpersonen, Contracten, Standaarden, Reviews, Komplianties, Moduleversies) now self-fetch and render rows. The column values are raw — noformatter/widget/ aggregate wired yet.Ask
src/services/formatters.js(procest is the reference) and pass it as:formatterstoCnAppRootinApp.vue. Preferwidget:"badge"(built in) for status columns.Contracten—statuscolumn →widget:"badge"Standaarden—status(andcategorie?) →widget:"badge"/ formatterKomplianties(compliance) — its status field →widget:"badge"formatter(or wait for the built-indateformatter — nextcloud-vue#224)aggregatecolumn where useful — e.g. a Standaard's "N implementations" or an Organisatie's contactpersonen count (noteOrganisatiesis currentlytype:"custom"; converting it totype:"index"+config.cardComponent:"OrganisatieCard"is tracked separately — the OrganisationModal/AddContactpersoonModal/status-dialog flow around it is what keeps it custom for now).Part of the fleet manifest-index wave (pipelinq #351, procest #436, scholiq #71). Non-production → auto-merge OK once CI is green.