Skip to content

feat(checks): default comparison key to trace.last.outputs - #2663

Closed
davidberenstein1957 wants to merge 2 commits into
mainfrom
feat/unify-extraction-keys
Closed

feat(checks): default comparison key to trace.last.outputs#2663
davidberenstein1957 wants to merge 2 commits into
mainfrom
feat/unify-extraction-keys

Conversation

@davidberenstein1957

@davidberenstein1957 davidberenstein1957 commented Jul 29, 2026

Copy link
Copy Markdown
Member

Summary

  • Default ComparisonCheck.key to trace.last.outputs so Equals(expected_value=...) (and siblings) match judge DX without an explicit key=
  • Document built-in extraction parameters in libs/giskard-checks/README.md
  • Add unit tests for default key resolution
  • No param renames/aliases in this PR (current answer_key / text_key names kept)

Closes #2659

Test plan

  • make test-unit PACKAGE=giskard-checks (757 passed, 4 skipped)
  • Pre-commit hooks (ruff, basedpyright, detect-secrets)
  • Spot-check: Equals(expected_value="Paris") against a scenario whose last outputs are "Paris"

Align Equals and other comparison checks with judges so callers can omit
key= when reading the last interaction outputs. Document extraction
parameters for built-ins in the checks README.

Closes #2659
Reformat README snippets so make check passes with ruff format on CI.
@kevinmessiaen kevinmessiaen added this to the V3-RC milestone Aug 12, 2026
@davidberenstein1957

Copy link
Copy Markdown
Member Author

Superseded by #2754, which includes this default plus the param renames, and has no conflicts. Closing in favor of that PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

feat(checks): unify extraction key parameters and defaults

2 participants