Chore: Prove able to fetch all fields in EvaluationContext #37
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 tasks
Codecov Report
@@ Coverage Diff @@
## main #37 +/- ##
=======================================
Coverage 99.33% 99.33%
=======================================
Files 15 15
Lines 303 303
Branches 24 24
=======================================
Hits 301 301
Partials 2 2 📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
The current implementation of the EvaluationContext is based on a dictionary. This is a list of key-value pairs. Able to use Linq based methods to iterate, fetch, manipulate and aggregate Spec 3.1.3 The evaluation context MUST support fetching the custom fields by key and also fetching all key value pairs. Signed-off-by: Benjamin Evenson <2031163+benjiro@users.noreply.github.com>
benjiro
force-pushed
the
chore/add-test-to-prove-121
branch
from
9bbb554
to
7eb400c
Compare
toddbaert
approved these changes
Aug 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current implementation of the EvaluationContext is based on
a dictionary. This is a list of key-value pairs. Able to use
Linq based methods to iterate, fetch, manipulate and aggregate
Spec 3.1.3 The evaluation context MUST support fetching the custom fields by key and also fetching all key value pairs.