Maybe we need to adapt the routing logic to better reflect the different aspect of the UI.
For example let's consider the URL of a particular attempt of a particular run. It will look something like:
workflows/<workflow_name>/<run_id>/<attempt_id>/timeline
And it makes sense.
However, if the user where to navigate from there to workflows/<workflow_name>/<run_id>/<attempt_id> he would reach 404notFound since it indeed represent nothing in our current logic. It is not a big issue as long as we don't display breadcrumbs for navigation, and as long as the user does not manually enters such adresses.
But we might want to refine the routing in the App to avoid such confusion
Maybe we need to adapt the routing logic to better reflect the different aspect of the UI.
For example let's consider the URL of a particular attempt of a particular run. It will look something like:
workflows/<workflow_name>/<run_id>/<attempt_id>/timelineAnd it makes sense.However, if the user where to navigate from there to
workflows/<workflow_name>/<run_id>/<attempt_id>he would reach 404notFound since it indeed represent nothing in our current logic. It is not a big issue as long as we don't display breadcrumbs for navigation, and as long as the user does not manually enters such adresses.But we might want to refine the routing in the App to avoid such confusion