Schedule item-local import scopes
This commit is contained in:
@@ -936,11 +936,14 @@ version-callback order. Ordinary mapping contributions in a main tier are assemb
|
||||
dependency-first: ConfigKit selects the lexically smallest stable source key among
|
||||
the contributions whose imports are complete. Independent branches may interleave,
|
||||
and the main body may be assembled after its imports. Sequence-item contributions
|
||||
retain their declaration order and local helper scope; they are not flattened into
|
||||
this ordinary mapping schedule. Assembly order never permits replacement. Required
|
||||
missing paths fail; `optional: true` suppresses only target nonexistence, not invalid
|
||||
paths, containment failures, directories, permissions, parse errors, or composition
|
||||
errors.
|
||||
in that tier are nodes in the same schedule; each selected item first assembles its
|
||||
own strict mapping scope, with helpers before the bodies that import them. Those
|
||||
local scopes do not use application collection policies and are not flattened into
|
||||
the outer schedule. Item positions and diagnostic paths follow the resulting
|
||||
assembly order.
|
||||
Assembly order never permits replacement. Required missing paths fail; `optional:
|
||||
true` suppresses only target nonexistence, not invalid paths, containment failures,
|
||||
directories, permissions, parse errors, or composition errors.
|
||||
|
||||
Glob declarations use the slash-based Go `path.Match` grammar: `*`, `?`, character
|
||||
classes, and backslash escapes are supported, while recursive `**` syntax is invalid.
|
||||
|
||||
Reference in New Issue
Block a user