[ADE-66] Add error handling and animation components to ProcessingPage for improved user feedback #90
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 enhances the
ProcessingPageby introducing better error handling, modularizing components, and improving the user experience with animations and error states. Key changes include the addition of new components for error and animation handling, refactoring the status-checking logic, and updating the SCSS for styling.Component Modularization and Reusability:
ProcessingAnimationcomponent to encapsulate the animation and processing message. (frontend/src/pages/Processing/components/ProcessingAnimation.tsx)ProcessingErrorcomponent to handle and display error states with retry and upload actions. (frontend/src/pages/Processing/components/ProcessingError.tsx)Error Handling Improvements:
clearStatusCheckIntervalfunction for better cleanup and error handling. (frontend/src/pages/Processing/ProcessingPage.tsx) [1] [2]handleRetryfunction. (frontend/src/pages/Processing/ProcessingPage.tsx)Styling Enhancements:
frontend/src/pages/Processing/ProcessingPage.scss)Code Simplification:
useEffectto make it reusable for retry attempts. (frontend/src/pages/Processing/ProcessingPage.tsx)These changes improve code readability, maintainability, and the overall user experience on the
ProcessingPage.Does this PR introduce a breaking change?
{...}
What needs to be documented once your changes are merged?
{...}
Additional Comments
{...}