[stable-4.7] Add a 404 Dispatch page, handle some old galaxy URLs (#4090) #4121
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.
Backport #4090
old galaxy UI base path is /, /{namespace}/{name}/ is a valid old galaxy URL
new galaxy UI base path is /ui/, and URLs for collections are different from URLs for legacy roles
we still want to support old URLs, so, when navigating to
(new-galaxy)/foo/bar/
:/ui/
base path, and redirect to/ui/dispatch?pathname=/foo/bar
Issue: AAH-2342
fix Documentation link duplicate key
list collections and roles, show as list items
simplify standalone redirect
add/use feature flags, links to all collections/role when none found
dispatch empty state top bullseye
dispatch - use EmptyStateNoData
(cherry picked from commit e0265b4)