add support for object returned from invoke api, add tests#104
Merged
Conversation
test/fixtures/vcr_cassettes/eval_functions/scorer_structured_response.yml
Outdated
Show resolved
Hide resolved
delner
requested changes
Feb 17, 2026
…nch / fix tests to align with real usage
… what the code scorer returns
a405e5a to
22820e9
Compare
Collaborator
|
This was released in v0.1.4. |
This file contains hidden or 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
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.
Summary
The Functions.scorer method attempts to expects the invoke API to return a number or a number string. It can actually return an object with metadata and the method is not setup to parse that e.g.
Steps to Reproduce
score = scorer.call(test[:input], test[:expected], test[:output], {})Expected
The scorer should return the correct score.
Observed
The scorer returns 0.0.