-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[Maps] Show empty list when all saved maps in list deleted #95126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Maps] Show empty list when all saved maps in list deleted #95126
Conversation
|
Pinging @elastic/kibana-gis (Team:Geo) |
|
Is redirecting to new map required? I find it is kind of jolting. How about just showing an empty state like visualize and dashboard? |
Because we'd end up in an orphaned state/route situation. Maps currently redirects if a user lands on |
|
I think that is ok to be on a route that would change if refreshed. As a user, I would not expect deleting the last map to re-route me to a new map. It just seems like a weird interaction. Maybe we should re-consider the reroute to a new map if there are no map saved objects. Maybe we should strive for consistency with dashboard and visualize and always show a landing page. |
As a user, I would expect first consistency within the app and then more broadly consistency within Kibana. I think the weirdness you're referencing is equally applicable to the normal flow, I address this a little more below.
Agreed. I've been on the fence on whether or not the redirect makes sense for about as long as it's been in place. I've created a separate issue to address it #95178. |
Thanks for opening the issue. I would think these are linked and the fix for #94638 is not to redirect but to have an empty listing view. |
I believe they're related but separate issues. The goal of the fix for #94638 should be to put the user into a usable and consistent route/state on delete of all maps saved objects. As it currently stands in the Maps app, we define that useable and consistent state of |
|
@elasticmachine merge upstream |
…ect-on-list-delete
…njcaldwell/kibana into fix-missing-redirect-on-list-delete
…ect-on-list-delete
src/plugins/kibana_react/public/table_list_view/table_list_view.tsx
Outdated
Show resolved
Hide resolved
lizozom
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM once green
|
@elasticmachine merge upstream |
|
After some offline conversation I've rolled this back to just the changes to the table list view component. We can handle any further changes to the routing redirect when we address #94638 |
nreese
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
code review
💚 Build SucceededMetrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: |
…5126) Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
…5126) Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Fixes #94638. The logic to redirect to a different URL was handled one component higher and only on initial load of the list component/page. This PR: