feat!: classification facets come from the configuration #26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/24-configurable-facets"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #24
What
src/lib/facets.ts: reads the facets an instance declares ({ id, label, description?, weight? }, none by default), picks their values out of a document, a request or a task, filters and scores./api/curate,/api/extract: iterate over the declared facets. A value given for something that is not a declared facet is ignored./api/taxonomies: returns the declared facets; a new theme is no longer tagged with a domain name.AGENTS.mdnow states the system role (generic provider) and its neutral example domain.Breaking
/api/extractno longer readslatitude/altitude, which were accepted but never used.weightof each facet (default 20).Verified
yarn test: 83 tests pass, 9 new on the facets module.Not verified
@quatrain/ux-curation, whose types still name the former fields: they were not exercised here and will be replaced by facet-driven pages in the interface work (#25).Left as is
POC_WORKBOOK.md,docs/tickets/anddocs/guide-modaka-vs-modaka-hub.mdstill describe the first use case. They are historical notes; whether they stay in this repository is the maintainer's call.🤖 Generated with Claude Code