Fix 404 page when wrong filtered catalog is being used in execution results page #1414
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.
Description
This pull request addresses a bug that occurs when navigating to the checks catalog view and selecting a provider filter (e.g., "gcp," "kvm," or "aws") different from the previously executed provider. Proceeding to the cluster details view and clicking the "Show Results" button, a 404 error page is encountered.
The underlying issue is a slow loading of the catalog, which triggers the error. To resolve this behavior, the pull request introduces several changes. Firstly, a loading state is implemented to improve data handling and ensure proper catalog loading. Additionally, the loading transition is enhanced by incorporating the LoadingBox component, resulting in a smoother user experience.
Before Fix
Bug.webm
After Fix
bugFix.webm