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

do not limit eval time progression graph to 7d #250

Merged
merged 1 commit into from
Dec 3, 2024
Merged

Conversation

dinmukhamedm
Copy link
Member

@dinmukhamedm dinmukhamedm commented Dec 3, 2024

Important

Change default time range in route.ts from 7 days to unlimited for evaluation time progression data.

  • Behavior:
    • Change default timeRange in GET function in route.ts from 7 days (pastHours: 168) to unlimited (pastHours: 'all').
    • Affects evaluation time progression data retrieval when no specific time range is provided.

This description was created by Ellipsis for 91b740c. It will automatically update as commits are pushed.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

❌ Changes requested. Reviewed everything up to 91b740c in 25 seconds

More details
  • Looked at 13 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 0 drafted comments based on config settings.

Workflow ID: wflow_W1V6G1OGQwFZops5


Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

@@ -16,7 +16,7 @@ export const GET = async (request: NextRequest, { params }: { params: { projectI
const endDate = new Date(request.nextUrl.searchParams.get('endDate') ?? '');
timeRange = { start: startDate, end: endDate };
} else {
timeRange = { pastHours: 168 };
timeRange = { pastHours: 'all' };
Copy link
Contributor

Choose a reason for hiding this comment

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

The change from pastHours: 168 to pastHours: 'all' may cause issues since pastHours is expected to be a number. Consider handling the 'all' case differently, perhaps by using a different field or logic to represent an unlimited time range.

@dinmukhamedm dinmukhamedm merged commit 389ba36 into dev Dec 3, 2024
1 check passed
@dinmukhamedm dinmukhamedm deleted the eval-time-limit branch December 3, 2024 03:14
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.

1 participant