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.
Change
This pull request introduces improvements to the bookmarking functionality, error handling, and user experience in the processing flow. The most notable changes include refactoring the bookmark update logic, ensuring proper cleanup of intervals, and integrating an upload modal in the error handling component.
Bookmarking Functionality:
useToggleReportBookmarkhook to simplify the logic for updating the bookmark status in the report detail page by directly replacing the report if IDs match, improving code clarity and maintainability. (frontend/src/common/hooks/useReports.ts)Processing Flow Enhancements:
clearStatusCheckInterval()before starting a new interval in theProcessingPagecomponent to ensure proper cleanup of intervals and prevent potential memory leaks. (frontend/src/pages/Processing/ProcessingPage.tsx)Error Handling Improvements:
ProcessingErrorcomponent to include anUploadModalfor retrying uploads directly from the error screen. This involved adding state management for modal visibility and defining a callback to handle upload completion and navigate the user to the home page. (frontend/src/pages/Processing/components/ProcessingError.tsx) [1] [2] [3]Does this PR introduce a breaking change?
{...}
What needs to be documented once your changes are merged?
{...}
Additional Comments
{...}