Open
Description
Currently, when refreshing any page within the application, users are redirected to the /pods
page instead of remaining on the page they were viewing. This behavior disrupts the user experience and prevents users from accessing the intended content consistently.
Problem
- Users are redirected to the
/pods
page upon refreshing any page in the application. - This issue affects all pages, not just
/deployments
, and causes users to lose their current context and view.
Expected Behavior
- When a user refreshes any page, they should remain on that page and not be redirected to
/pods
. - The page should persist in its current state and content.
Steps to Reproduce
- Navigate to any page within the application (e.g.,
/deployments
,/services
, etc.). - Refresh the page using the browser’s refresh button or F5 key.
- Observe that the page redirects to
/pods
instead of staying on the current page.
Acceptance Criteria
-
Page Persistence:
- Refreshing any page should not redirect users to
/pods
. - Users should stay on the current page after a refresh.
- Refreshing any page should not redirect users to
-
State Maintenance:
- Ensure that the page content and state (if applicable) are preserved across refreshes.
-
Testing:
- Verify that refreshing any page consistently maintains the correct URL and page state.
- Test across different browsers and devices to ensure consistent behavior.
Additional Information
Investigate the current routing and page handling logic to determine why the redirection occurs on refresh. Ensure that the fix aligns with the application's routing strategy and does not impact other functionalities.