[Feature] Template library with typed templates and required-field contracts #3

Closed
opened 2026-07-14 20:08:42 +02:00 by zemion · 1 comment
Owner

Problem / User Need

GovOPlaN needs a template library that stores reusable templates with explicit template types and required fields, so modules know where templates can be used and whether data matches.

Acceptance Criteria

  • Templates can be saved in a reusable library.
  • Templates have types/usages that restrict where they can be used.
  • Templates declare required fields or data contracts.
  • Consumers can check whether their available data satisfies the template contract before use.
  • The UI makes missing fields and incompatible template types clear.

Notes / Decisions

Matching required fields to campaign/recipient/process data will need careful design.

## Problem / User Need GovOPlaN needs a template library that stores reusable templates with explicit template types and required fields, so modules know where templates can be used and whether data matches. ## Acceptance Criteria - Templates can be saved in a reusable library. - Templates have types/usages that restrict where they can be used. - Templates declare required fields or data contracts. - Consumers can check whether their available data satisfies the template contract before use. - The UI makes missing fields and incompatible template types clear. ## Notes / Decisions Matching required fields to campaign/recipient/process data will need careful design.
Author
Owner

Implemented and pushed in b65b905, with platform contracts in GovOPlaN/govoplan-core@e4d2d10.

Delivered:

  • typed reusable template catalogue with tenant/system/group/user scope, locale, status, usage/type metadata, and required input contracts;
  • immutable revisions, publication, optimistic concurrency, compatibility diagnostics, and audit/event evidence;
  • editor/library UI with compatibility checks, revision history, and permission-aware actions;
  • provider-neutral templates.catalog and templates.renderer capabilities.

Validation: 6 Templates backend tests, 2 Core contract tests, 120 Core module-system tests, Templates TypeScript, module permutations, and the full Core production WebUI build all pass.

Implemented and pushed in `b65b905`, with platform contracts in GovOPlaN/govoplan-core@`e4d2d10`. Delivered: - typed reusable template catalogue with tenant/system/group/user scope, locale, status, usage/type metadata, and required input contracts; - immutable revisions, publication, optimistic concurrency, compatibility diagnostics, and audit/event evidence; - editor/library UI with compatibility checks, revision history, and permission-aware actions; - provider-neutral `templates.catalog` and `templates.renderer` capabilities. Validation: 6 Templates backend tests, 2 Core contract tests, 120 Core module-system tests, Templates TypeScript, module permutations, and the full Core production WebUI build all pass.
zemion removed the codex/ready
status
ready
labels 2026-08-02 17:32:13 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-templates#3