Repository navigation
feat(scoring): export the deep-eval and category-score functions from the package root - #74
joelepper-netlify wants to merge 1 commit into
Conversation
… the package root runDeepEval, computeHeuristicSpeed, parseCategoryEvalResponse, computeCategoryScore, aggregateDimension and parseJsonFromText, with the DeepEvalOptions and CalibrationParams types, are now exported from the package root. The change is additive: no behavior change, no rename, and no exports map, so existing deep imports keep working. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Deploy Preview for axisproject ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for axis-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review.
 |
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title names the main change: the deep-eval and category-score functions are now exported from the package root. It also uses the conventional feat(scoring) prefix. The 86-character length is long … |
| Docstring Coverage | |
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2 files. (1 skipped: 1 … |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
| Description check | |
The pull request description clearly describes the root-level exports, exported types, additive API change, compatibility with existing deep imports, test coverage, and README update. These details ma… |
Full details: Title check
-
Explanation
The title names the main change: the deep-eval and category-score functions are now exported from the package root. It also uses the conventional feat(scoring) prefix. The 86-character length is long but still readable, and no vague terms are used.
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2 files. (1 skipped: 1 unsupported.)
Full details: Description check
-
Explanation
The pull request description clearly describes the root-level exports, exported types, additive API change, compatibility with existing deep imports, test coverage, and README update. These details match the changeset.
Finishing Touches
-
📝 Generate docstrings
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Linked repositories: Some configured repositories could not be included in this review. Cross-repository analysis may be incomplete. Please check linked-repository access and settings.
Comment @coderabbitai help to get the list of available commands.
When using AXIS as part of an orchestrated evaluation system we found that it's useful to be able to import some of the internals. THis PR adds those exports.
Exports
runDeepEval,computeHeuristicSpeed,parseCategoryEvalResponse,computeCategoryScore,aggregateDimensionandparseJsonFromText, with theDeepEvalOptionsandCalibrationParamstypes, from the package root. Callers that run per-category scoring with their own judge adapter can then import them without reaching intodist/.Additive only: no behavior change, no rename, and no
exportsmap, so existing deep imports keep working. A new test imports each export from the root. The README Programmatic API section describes them.🤖 Generated with Claude Code