Skip to content

Commit c4babd3

Browse files
authored
docs: clarify evaluation context in hook requirements (#330)
## This PR - clarify evaluation context in hook requirements ### Related Issues Fixes #328 ### Notes I added the clarification in the non-normative section. Hopefully, this addresses the ambiguity around what we mean by `evaluation context`. Signed-off-by: Michael Beemer <[email protected]>
1 parent baec39b commit c4babd3

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

specification/sections/04-hooks.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,8 @@ Hook context exists to provide hooks with information about the invocation and p
4949

5050
> Hook context **MUST** provide: the `flag key`, `flag value type`, `evaluation context`, `default value`, and `hook data`.
5151
52+
The `evaluation context` provided in the hook context refers to the **merged evaluation context** as specified in [Requirement 3.2.3](./03-evaluation-context.md#requirement-323).
53+
5254
#### Requirement 4.1.2
5355

5456
> The `hook context` **SHOULD** provide access to the `client metadata` and the `provider metadata` fields.

0 commit comments

Comments
 (0)