Expand description
EnhanceSetting — the internal model that configures an
EnhanceApplication.
The internal storage form is a BlueprintId ref: the store does not
hold the Blueprint body itself; that is resolved through
BlueprintStore. HTTP POST/PUT input goes through
EnhanceSettingInput and receives Blueprint data inline; the server
orchestrates a BPStore.write_new and converts to a Ref before
persisting.
Runtime parameters (ttl_secs, meta) live on EnhanceSetting. The
EnhanceApplication fetches the setting on every tick and picks up
changes, so setting edits act as a hot reload.
Structs§
- Enhance
Setting - Internal storage form — the view held by the store and by
EnhanceApplication. ABlueprintIdref plus runtime parameters. - Enhance
Setting Input - HTTP
POST/PUTinput shape — the caller’s view. Blueprint data is inline; the server doesBPStore.write_newand converts it to a Ref before persisting. - Enhance
Setting Meta - Extension metadata attached to an
EnhanceSetting. Placeholder — something will land here for certain, so the slot exists up front.