Clarify native imported step ordering
This commit is contained in:
@@ -169,7 +169,13 @@ pipelines:
|
||||
|
||||
Pipeline names are siblings within `pipelines`; nested mappings such as named
|
||||
artifact lanes also have their own sibling namespace. Distinct imported step IDs
|
||||
combine in source order; duplicate peer IDs conflict. Across an overlay or
|
||||
combine in ConfigKit's dependency-ready assembly order, not necessarily import
|
||||
declaration or acquisition order; duplicate peer IDs conflict. Ready contributions
|
||||
are selected by their stable source keys. See the pinned
|
||||
[import assembly contract](https://forge.maximumdirect.net/base-layer/configkit/src/commit/c1c7e87f2cdf77a0cbf3327831ac05578e756b9e/docs/config.md#explicit-imports)
|
||||
for full ordering semantics. In the complete example, the imported describe-session
|
||||
step precedes the importing body's extract-events step because an imported
|
||||
dependency is assembled before its importer. Across an overlay or
|
||||
inheritance, upsert replaces a matching step as a complete record in place and
|
||||
appends new IDs. It does not merge individual fields of a matching step. An
|
||||
identified record can itself use native `extends`. Authors may select `replace`
|
||||
|
||||
Reference in New Issue
Block a user