Skip to content

evaluation context requirement to allow fetching all custom fields #120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Aug 3, 2022
Merged

evaluation context requirement to allow fetching all custom fields #120

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
241a675
evaluation context requirement to allow fetching all custom fields
rgrassian-split Aug 2, 2022
995d4ad
Update specification/sections/03-evaluation-context.md
rgrassian-split Aug 2, 2022
a3492d4
include specification.json
rgrassian-split Aug 3, 2022
d296226
Merge branch 'evalContextFetchAll' of github.com:rgrassian-split/spec…
rgrassian-split Aug 3, 2022
da65524
fix spec
rgrassian-split Aug 3, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions specification.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -299,6 +299,13 @@
"RFC 2119 keyword": "MUST",
"children": []
},
{
"id": "Requirement 3.1.3",
"machine_id": "requirement_3_1_3",
"content": "The evaluation context MUST support fetching the custom fields by key and also fetching all key value pairs.",
"RFC 2119 keyword": "MUST",
"children": []
},
{
"id": "Requirement 3.2.1",
"machine_id": "requirement_3_2_1",
Expand Down
4 changes: 4 additions & 0 deletions specification/sections/03-evaluation-context.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,10 @@ The targeting key uniquely identifies the subject (end-user, or client service)

see: [structure](../types.md#structure), [datetime](../types.md#datetime)

#### Requirement 3.1.3

> The evaluation context **MUST** support fetching the custom fields by key and also fetching all key value pairs.

### Merging Context

#### Requirement 3.2.1
Expand Down