Design 27: a served own name with a default, or nested, is refused too (ADR 0346, review 224)
This commit is contained in:
@@ -290,7 +290,8 @@ the consumer's own, so the binding and the proxy name one host. Where the provid
|
|||||||
no such name (it has no public domain, or the endpoint is not reached publicly), the key is left out of
|
no such name (it has no public domain, or the endpoint is not reached publicly), the key is left out of
|
||||||
what the consumer is told, and `plan` says so on the provider's machine and under the consumer's need.
|
what the consumer is told, and `plan` says so on the provider's machine and under the consumer's need.
|
||||||
*How it is checked:* the module check refuses a served value naming a requirement the module does not
|
*How it is checked:* the module check refuses a served value naming a requirement the module does not
|
||||||
contribute to or a fact other than those names; the controller's unit tests for both paths and for the
|
contribute to or a fact other than those names, one with a default (`|default:`), and one nested in a
|
||||||
|
list or an object; the controller's unit tests for both paths and for the
|
||||||
left-out key, each run against the unchanged controller first.
|
left-out key, each run against the unchanged controller first.
|
||||||
|
|
||||||
## How a definition reads what was resolved
|
## How a definition reads what was resolved
|
||||||
|
|||||||
Reference in New Issue
Block a user