Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
chore: update nextjs to v15 #2513
chore: update nextjs to v15 #2513
Changes from all commits
9cae809
5ff2b44
00c7ca8
9cf449f
5cb47d3
5704fc0
f21d1b5
246b714
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Add error handling and optimize Promise resolution
The current implementation could be improved with proper error handling and optimization:
Consider this implementation:
📝 Committable suggestion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Promise-based params handling is inconsistent across route handlers
The verification reveals inconsistent patterns in handling route parameters across the codebase:
Some pages use the
use
hook with Promise-based params:/workflows/[workflow_id]/page.tsx
/workflows/[workflow_id]/runs/[workflow_execution_id]/page.tsx
/workflows/preview/[workflowId]/page.tsx
/workflows/preview/page.tsx
While others use async/await pattern:
/workflows/builder/[workflowId]/page.tsx
/incidents/[id]/*
pages/dashboard/[id]/page.tsx
For consistency, consider standardizing the approach across all route handlers, preferably using the async/await pattern which is more commonly used in the codebase.
🔗 Analysis chain
Verify consistent implementation across route handlers
Let's verify that this pattern of handling promise-based params is consistently implemented across other route handlers in the application.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 163
Script:
Length of output: 20371