-
Notifications
You must be signed in to change notification settings - Fork 23
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
Parse JSON in JSONDiff #99
Conversation
Braintrust eval reportAutoevals (semantic-json-1730742427)
|
Braintrust eval reportAutoevals (semantic-json-1730701127)
|
'{"o1": {"y": 2, "x": 1}}', | ||
0.83333, | ||
), | ||
( |
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.
This test case is identical to the one above it.
js/json.test.ts
Outdated
expected: 0.83333, | ||
}, | ||
{ | ||
a: '{"o1": {"x": 2, "y": 2}}', |
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.
This test case is identical to the one above.
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.
Thanks for flagging, just tweaked it
Braintrust eval report
|
By popular demand... if the string looks like JSON, treat it as such. This is very common when comparing an LLM generated json string to an expected value.