Adopt ConfigKit v0.5.0 inheritance
This commit is contained in:
@@ -26,7 +26,7 @@ The maintained [minimal configuration](../examples/config.yml),
|
||||
|
||||
## Application Configuration File
|
||||
|
||||
Configuration is decoded by ConfigKit v0.4.2 as strict YAML. Unknown fields,
|
||||
Configuration is decoded by ConfigKit v0.5.0 as strict YAML. Unknown fields,
|
||||
empty files, multiple YAML documents, and YAML aliases/anchors are rejected.
|
||||
An explicit empty string is a value: it clears a file-provided optional path
|
||||
or, for required `prompt_dir`, fails the command's prerequisite. A scalar
|
||||
@@ -111,6 +111,27 @@ History includes replaced and removed values; `show` presents the final
|
||||
resolved snapshot. Neither renderer looks up credential bytes, and neither
|
||||
claims to identify arbitrary secrets in unclassified parameter values.
|
||||
|
||||
### Application mapping inheritance
|
||||
|
||||
Application input mappings may use ConfigKit's `extends: sibling-name`
|
||||
directive to inherit settings from a sibling mapping. Inheritance is resolved
|
||||
after imports, a selected overlay, and explicit CLI overrides have been
|
||||
assembled, and before typed decoding. Explicit child values replace inherited
|
||||
values, and `extends: null` cancels inheritance. Parents remain ordinary
|
||||
configured entries; for example, a parent backend is still registered and
|
||||
validated with its child. See the pinned [ConfigKit v0.5.0 inheritance
|
||||
contract](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/dc09959cca4e105f49ec316c6d4ba585bd2340bd/docs/config.md#sibling-inheritance)
|
||||
for detailed semantics.
|
||||
|
||||
`extends` is reserved across application input mappings, not only under
|
||||
`backends`; quoting the key does not make it ordinary data. This can affect a
|
||||
mapping entry named `extends` or a literal provider parameter with that name.
|
||||
Rename an application-owned name where appropriate. A provider-required literal
|
||||
key cannot generally be renamed without provider support, and this ConfigKit
|
||||
version has no escape or opt-out; a concrete need must be addressed upstream.
|
||||
The directive does not apply to separately parsed Promptkit definitions or
|
||||
HTTP request payloads.
|
||||
|
||||
## Custom Backends
|
||||
|
||||
Use `backends` when a profile selects an application-defined backend ID:
|
||||
|
||||
Reference in New Issue
Block a user