Clarify companion binding ownership
This commit is contained in:
@@ -38,8 +38,9 @@ Start with one file, then choose the tasks your application needs:
|
||||
- Use `LoadLayered` when several inputs should supply lower-priority defaults
|
||||
beneath the main source. Each underlay group combines its inputs strictly.
|
||||
Each [`Input`](../../layered.go) owns its source, filesystem, destination, and
|
||||
import choice. Main-relative bindings and overlay context selection are
|
||||
available in [`LayeredOptions`](../../layered.go).
|
||||
import choice. Set `Input.MainRelative` on a companion underlay to use the
|
||||
main input's filesystem context. Overlay context selection belongs to
|
||||
[`LayeredOptions`](../../layered.go).
|
||||
- Load-wide rules belong to [`Options`](../../lifecycle.go) or
|
||||
[`LayeredOptions`](../../layered.go): the application definition (including
|
||||
version policy), import defaults, and explicit overrides. These do not turn
|
||||
|
||||
Reference in New Issue
Block a user