Skip to content
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

feat: add base evaluator and correctness evaluator #559

Merged
merged 15 commits into from
Feb 26, 2024

Conversation

EmanuelCampos
Copy link
Collaborator

No description provided.

Copy link

changeset-bot bot commented Feb 22, 2024

🦋 Changeset detected

Latest commit: abf3482

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
llamaindex Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

vercel bot commented Feb 22, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
llama-index-ts-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 26, 2024 0:37am

examples/evaluation/correctness.ts Outdated Show resolved Hide resolved
@@ -0,0 +1,42 @@
import {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about adding

  1. README for the new evaluation folder
  2. docs for using CorrectnessEvaluator
    ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marcusschiesser I'd have it on the pipeline

packages/core/src/evaluation/types.ts Outdated Show resolved Hide resolved
packages/core/src/evaluation/Correctness.ts Outdated Show resolved Hide resolved
packages/core/src/evaluation/Correctness.ts Outdated Show resolved Hide resolved
Comment on lines 20 to 23
evaluateResponse(
query: string,
response: Response,
): Promise<EvaluationResult>;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks to me like this is not needed (if evaluate would use a parameter object)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@marcusschiesser was missing a few lines of code that make the DX better with evaluateResponse

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wondering about change BaseEvaluator to a class then we can have this evaluateResponse on the base class

@himself65
Copy link
Member

My recent commit might affect your code. Please add .js extensions for each import.

And read https://www.typescriptlang.org/docs/handbook/modules/reference.html#node16-nodenext-1 to know what's the reason.

If you have any question please ping me

@EmanuelCampos EmanuelCampos merged commit c8396c5 into main Feb 26, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants