[Feature] Allow module configuration so behavior can be controlled through settings #37

New Issue

2026-07-06T11:32:08+02:00

zemion commented

2026-07-06 11:32:08 +02:00

Imported from the consolidated GovOPlaN product backlog.

Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/backlog.md
Line: 223
Section: Milestones > Milestone 13 - Full Module Administration
Source status: OPEN.

Imported backlog item:

- [ ] Allow module configuration so behavior can be controlled through settings.

Imported from the consolidated GovOPlaN product backlog. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/backlog.md` - Line: `223` - Section: `Milestones > Milestone 13 - Full Module Administration` - Source status: `OPEN.` Imported backlog item: ```markdown - [ ] Allow module configuration so behavior can be controlled through settings. ```

zemion added this to the Milestone 13 - Full Module Administration milestone 2026-07-06 13:07:12 +02:00

zemion commented

2026-07-10 22:20:07 +02:00

Codex State: progress

Summary

Existing pieces cover parts of this: enabled module state, admin module-management endpoints, module manifests, and configuration package providers.

Next / Blocked

Define a generic module settings contract: manifest-declared setting schema, defaults, validation/preflight, runtime injection, API exposure, admin UI renderer, and audit/configuration-control integration.
Only close after at least one non-core module uses the generic contract instead of bespoke settings routes.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Existing pieces cover parts of this: enabled module state, admin module-management endpoints, module manifests, and configuration package providers. ### Next / Blocked - Define a generic module settings contract: manifest-declared setting schema, defaults, validation/preflight, runtime injection, API exposure, admin UI renderer, and audit/configuration-control integration. - Only close after at least one non-core module uses the generic contract instead of bespoke settings routes. Suggested status label: `status/in-progress`

zemion added the area/module-system codex/needs-human module/core

priority

p2

source/backlog-import

labels 2026-07-29 14:15:18 +02:00

zemion commented

2026-07-30 17:46:46 +02:00

Module-settings discovery/UI slice pushed in Core f0898fc, Access e8ea347, and the contributing module commits.

AdminSectionContribution now declares moduleId, kind (management/settings) and an optional parent identity. Access aggregates available/authorized contributions into scope and module branches, while each module still owns and renders its settings page. This preserves optional-module boundaries and supports existing full-page settings today; named embedded settings slots remain future control-plane work under GovOPlaN #25.

Module-settings discovery/UI slice pushed in Core `f0898fc`, Access `e8ea347`, and the contributing module commits. `AdminSectionContribution` now declares `moduleId`, `kind` (`management`/`settings`) and an optional parent identity. Access aggregates available/authorized contributions into scope and module branches, while each module still owns and renders its settings page. This preserves optional-module boundaries and supports existing full-page settings today; named embedded settings slots remain future control-plane work under GovOPlaN #25.

zemion commented

2026-07-31 01:22:08 +02:00

Completed

Module-owned settings are now discovered through typed admin-section contributions carrying module, kind, parent, visibility, and authorization metadata; modules render their own settings without Core importing them. Access composes the available sections into the administration tree, and module-permutation coverage protects optional combinations. The richer canonical field/action inventory remains tracked by GovOPlaN #25, not by this original module-settings ticket.

## Completed Module-owned settings are now discovered through typed admin-section contributions carrying module, kind, parent, visibility, and authorization metadata; modules render their own settings without Core importing them. Access composes the available sections into the administration tree, and module-permutation coverage protects optional combinations. The richer canonical field/action inventory remains tracked by [GovOPlaN #25](https://git.add-ideas.de/GovOPlaN/govoplan/issues/25), not by this original module-settings ticket.

zemion closed this issue

2026-07-31 01:22:08 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-core#37