-
Notifications
You must be signed in to change notification settings - Fork 0
feat(Mappers): Add mapper test cases #46
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.
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
base: main
Are you sure you want to change the base?
Conversation
…conversion Co-authored-by: Claude <noreply@anthropic.com>
9347dad to
c2748d4
Compare
|
Is this part of the current sprint? |
It was intended to, but we ultimately decided to release without this. |
| # Engine Test Data | ||
|
|
||
| > [!NOTE] | ||
| > Test case files may contain descriptions in JSON5-compliant comments. Test implementations should be ready to parse JSON5. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this say jsonc instead of json5?
| @@ -0,0 +1,286 @@ | |||
| { | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this file does not have any comments? It can be just named .json?
Mapper test cases validate conversion from environment documents to evaluation contexts.
Changes
mapper_test_cases/directory with test dataWarning
Mapper tests exist only to support safe deprecation of the environment document.
Review effort: 2/5