Minor fixes in evals

[dinmukhamedm]

• Make target optional
• Fix eval time progression graph
• Fix eval scores graph

---

Important

This pull request includes minor fixes and enhancements in evaluation handling, graph rendering, and blog code highlighting across backend and frontend components.

• Backend Fixes:
  • In evaluation_scores.rs, fixed SQL query condition to correctly handle bucket counts in evaluation scores.
  • Made target field optional in EvaluationDatapointResult in utils.rs.
• Frontend Fixes:
  • In route.ts, changed default timeRange to { pastHours: 'all' } for evaluation progression.
  • Added PreHighlighter component in page.tsx for enhanced code block rendering in blog posts.
  • Adjusted blog layout in page.tsx to improve visual presentation.
• UI Enhancements:
  • Added copy button to CodeHighlighter in code-highlighter.tsx for easier code copying.

^{This description was created by for fb50618. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to fb50618 in 18 seconds

More details

• Looked at 179 lines of code in 7 files
• Skipped 0 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. app-server/src/ch/evaluation_scores.rs:220

• Draft comment:
  Ensure that intervals.interval_num is correctly bound and used in the query to avoid logical errors. This change improves the logic to avoid counting the same value twice across different intervals.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The change in app-server/src/ch/evaluation_scores.rs at line 220 introduces a condition that checks if the value equals a specific value and if the interval number matches. This is a logical improvement to avoid counting the same value twice across different intervals. However, the SQL query should ensure that the intervals.interval_num is correctly bound and used in the query to avoid logical errors.

2. frontend/app/api/projects/[projectId]/evaluation-groups/[groupId]/progression/route.ts:19

• Draft comment:
  Verify that TimeRange supports a string value like 'all'. Changing from pastHours: 168 to pastHours: 'all' might cause issues if TimeRange does not support string values.
• Reason this comment was not posted:
  Confidence changes required: 50%
  In frontend/app/api/projects/[projectId]/evaluation-groups/[groupId]/progression/route.ts, the change from pastHours: 168 to pastHours: 'all' at line 19 might cause issues if the TimeRange type does not support a string value. This should be verified to ensure compatibility.

3. frontend/components/blog/pre-highlighter.tsx:17

• Draft comment:
  Add a check to ensure children.props.className is defined and contains a language class to avoid runtime errors.
• Reason this comment was not posted:
  Confidence changes required: 50%
  In frontend/components/blog/pre-highlighter.tsx, the code assumes that children.props.className is always defined and contains a language class. This might lead to runtime errors if className is undefined or does not contain a language class. A check should be added to handle such cases gracefully.

Workflow ID: wflow_gnzGyeFZjyPqem11

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.