Repository navigation
Open
Labels
openspecOpenSpec-driven changeOpenSpec-driven changeopenspec:tasksOpenSpec phase: TasksOpenSpec phase: Tasks
Description
⚠️ OpenSpec-managed issue — this content is automatically synced
from theopenspec/directory. Manual edits will be overwritten on next sync.
Artifacts
Summary
A user adding a customer or a supplier types a company name or KvK number,
picks the company from the KvK Handelsregister, and the legal name, trade name
and address fill in. Shillinq declares the lookup on two properties and turns
the KvK connection on. The lookup itself is integriq's and the key is
openregister's; both already ship.
Specs
Tasks
- 1.1 Add
x-openregister-property-sourcewith the customer fill map of design D2 toCustomerMaster.kvkNumberinlib/Settings/register.d/add-shillinq-bookkeeping-compliance.json, and with the supplier fill map toPayee.kvkNumberinlib/Settings/register.d/bookkeeping-accounts-payable-core.json; regenerateshillinq_register.jsonif the build merges fragments (REQ-KVKL-001, REQ-KVKL-002). Verify:npm run check:registers; a PHPUnit test that reads both fragments and asserts providerkvk, modedefaultand every fill target is a declared property of its schema. - 1.2 Import the register on a dev instance and read both schemas from openregister (REQ-KVKL-001). Verify:
propertyMetadata.kvkNumbernameskvkon both;grep 'PARTIAL IMPORT'in the log finds nothing; record the output in the PR body. - 2.1 Switch the
kvkentry inlib/Settings/connections.jsonon per design D3 (REQ-KVKL-003). Verify: the existing connections test (ConnectionReportServicetests) passes with the entry available; integriq's connections overview lists it as not set up yet on the dev instance. - 3.1 With the KvK source linked (sandbox or the integriq seed), add a supplier from the KvK and read the filled name and address; type a name first and confirm the replace question (REQ-KVKL-002). Verify: Playwright test tagged with
@e2ereferences to the scenarios; skipped with a stated reason while the renderer is absent. - 3.2 With no source linked, add a customer with a typed number and confirm it saves with the not-set-up message (REQ-KVKL-003). Verify: Playwright, same tagging.
- 4.1 Add "Look a company up in the KvK" to the customers and suppliers user guide pages in
docs/, and the unconfigured message string with its Dutch translation inl10n/(REQ-KVKL-003). Verify:npm run test:l10n.
Design
See design.md for technical design details.
Synced from openspec/changes/contacts-kvk-lookup by OpenSpec workflow
App: shillinq
Metadata
Metadata
Assignees
Labels
openspecOpenSpec-driven changeOpenSpec-driven changeopenspec:tasksOpenSpec phase: TasksOpenSpec phase: Tasks
Activity