[OpenSpec] insight-supplier-facet #1126

⚠️ OpenSpec-managed issue — this content is automatically synced
from the openspec/ directory. Manual edits will be overwritten on next sync.

Artifacts

• ✅ Metadata
• ✅ Proposal
• ✅ Specs
• ✅ Design
• ✅ Tasks
• 🔲 Plan
• 🔲 Review

Summary

A municipal information manager on the Applications page can narrow the list by reference component, standard, application service and domain, with a count next to every value. They cannot narrow it by supplier, which is the other example the matrix row names and the first facet GEMMA Softwarecatalogus users expect. This change adds Supplier as a fifth facet on /modules and /diensten, computed by the same service, counted the same way and kept in the URL and in saved views like the other four.

Specs

• 📄 supplier-facet

Tasks

• Implement
• Test (PHPUnit tests/Unit/Service/FacetServiceTest.php)
• Implement
• Test (PHPUnit tests/Unit/Controller/FacetControllerTest.php and tests/Unit/Service/FacetServiceTest.php, vitest src/services/facets.spec.js)
• Implement
• Test (vitest tests/vitest/facetSchema.spec.js and tests/vitest/facetStore.spec.js, Playwright tests/e2e/spec-coverage/supplier-facet.spec.ts)
• Implement
• Test (Playwright tests/e2e/spec-coverage/supplier-facet.spec.ts against the demo data)

Design

See design.md for technical design details.

Synced from openspec/changes/insight-supplier-facet by OpenSpec workflow
App: stackiq