factor out function wrapper to module function #9

Closed

kiara wants to merge 4 commits from data-model-factor-out-wrapper into deployment-data-model-with-tests

Author	SHA1	Message	Date
Kiara Grouwstra	d066b1d55c	rename internal `implementation` to `declare`, mirroring `apply`	2025-08-18 10:24:09 +02:00
Kiara Grouwstra	efbe7deddd	factor common logic back out note that i worked around the question of how to delegate part of the options to the consumer by creating aliases for different parts of the function slot filling. i've been pretty arbitrary about this so far tho, and mostly to preserve existing interfaces, rather than out of conscious UX design per se. so the interface can def change still, but at least the _user_'s side is more DRY now!	2025-08-17 23:17:55 +02:00
Kiara Grouwstra	fb004a4d4c	combine UX with parameter type-check - DRYing TODO	2025-08-17 17:24:43 +02:00
Kiara Grouwstra	6fa9c40662	factor out function wrapper to module function note that this does not yet contain the 'type check', as this does not function yet. this could be added in `data-model.nix` like: ```nix function-type-check = mkOption { type = application.config.config-mapping.function-type; readOnly = true; default = input: { inherit input; output = application.config.config-mapping.implementation-type input; }; }; ``` ... or even to `function.nix` itself, like: ```nix function-type-check = mkOption { type = config.function-type; readOnly = true; default = input: { inherit input; output = config.implementation-type input; }; }; ```	2025-08-01 17:56:35 +02:00