Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

User-details pane displays perpetual loading-spinner when API returns 4xx

Description

Summary: The UserDetail pane shows a loading spinner when it should show an error message if the selUser request fails with a 4xx response other than 404.

Details: userNotFound() checks for 404 but not other 4xx responses, resulting in the misleading display of the loading-spinner for a request that is, in fact, complete. UserDetail should be able to handle any 4xx or 5xx response. It’s fine if we want 404 to be a special case, and we may not need separate translations and handlers for each other erroor, but we should at least present the response in the UI so the user knows the request failed.

Environment

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Zak Burke February 19, 2024 at 1:37 PM

, this isn’t easy because it relies on a backend API returning a specific, non-404 response, so you’d have to stub out that response. But you can see very clearly in the code that the only non-200 response it handles is 404. That code needs to handle anything >= 400.

Irina Pokhylets February 19, 2024 at 11:54 AM

Hi,
, could you please provide steps for reproducing and screenshots?

Details

Assignee

Reporter

Labels

Priority

Story Points

Development Team

Volaris

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created February 15, 2024 at 5:19 PM
Updated September 30, 2024 at 7:37 AM
TestRail: Cases
TestRail: Runs

Flag notifications