Bug #14990

[Navigation] Attempting to navigate to non-existent path not handled

Added by Peter Amstutz 5 months ago. Updated 2 days ago.

Status:
New
Priority:
Normal
Assigned To:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Attempting to navigate to an unknown path should produce an error message. Examples where there is not currently the case include:

https://workbench2.c97qk.arvadosapi.com/project/c97qk-j7d0g-4xans0bhlqiyrkv - This spins forever ("project" misspelled)
https://workbench2.c97qk.arvadosapi.com/projects/c97qk-j7d0g-4xans0bhlqiyrk - also spins forever (last character of uuid is missing)
https://workbench2.c97qk.arvadosapi.com/projects/c97qk-j7d0g-4xans0bhlqiyrkk - loads an empty project page instead of returning an error saying non-existent project

Possibly relevant - https://stackoverflow.com/questions/32128978/react-router-no-not-found-route

History

#1 Updated by Peter Amstutz 5 months ago

  • Status changed from New to In Progress

#2 Updated by Peter Amstutz 5 months ago

  • Subject changed from Attempting to navigate to non-existent path spins forever to Attempting to navigate to non-existent path not handled
  • Description updated (diff)

#3 Updated by Peter Amstutz 5 months ago

  • Status changed from In Progress to New

#4 Updated by Chrystian Klingenberg 3 months ago

  • Target version set to Backlog Q1, Q2

#5 Updated by Chrystian Klingenberg 2 months ago

  • Target version changed from Backlog Q1, Q2 to Workbench2 Q3, Q4

#6 Updated by Chrystian Klingenberg 2 months ago

  • Subject changed from Attempting to navigate to non-existent path not handled to [Navigation] Attempting to navigate to non-existent path not handled

#7 Updated by Tom Morris 2 days ago

  • Description updated (diff)

Also available in: Atom PDF