Skip to content

Commit

Permalink
Document context merging order for before hook ctx (#125)
Browse files Browse the repository at this point in the history
Signed-off-by: Justin Abrahms <[email protected]>
Co-authored-by: Todd Baert <[email protected]>
Signed-off-by: Justin Abrahms <[email protected]>
  • Loading branch information
justinabrahms and toddbaert committed Aug 9, 2022
1 parent 0b272d5 commit 3891551
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion specification.json
Original file line number Diff line number Diff line change
Expand Up @@ -400,7 +400,7 @@
{
"id": "Requirement 4.3.4",
"machine_id": "requirement_4_3_4",
"content": "When `before` hooks have finished executing, any resulting `evaluation context` MUST be merged with the invocation `evaluation context` with the invocation `evaluation context` taking precedence in the case of any conflicts.",
"content": "When `before` hooks have finished executing, any resulting `evaluation context` MUST be merged with the existing `evaluation context` in the following order: before-hook (highest precedence), invocation, client, api (lowest precedence).",
"RFC 2119 keyword": "MUST",
"children": []
},
Expand Down
2 changes: 1 addition & 1 deletion specification/sections/04-hooks.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ EvaluationContext | void before(HookContext, HookHints);
#### Requirement 4.3.4

> When `before` hooks have finished executing, any resulting `evaluation context` **MUST** be merged with the invocation `evaluation context` with the invocation `evaluation context` taking precedence in the case of any conflicts.
> When `before` hooks have finished executing, any resulting `evaluation context` **MUST** be merged with the existing `evaluation context` in the following order: before-hook (highest precedence), invocation, client, api (lowest precedence).
#### Requirement 4.3.5

Expand Down

0 comments on commit 3891551

Please sign in to comment.