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
ui: Various empty state improvements/fixups #11892
Conversation
Previous to this fix we would not show a more tailored message for when you empty result set was due to a user search rather than an empty result set straight from the backend
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.
Pair reviewed
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/534820. |
🍒✅ Cherry pick of commit 2c1eb05 onto |
* ui: Add login button to per service intentions for zero results * Add login button and consistent header for when you have zero nodes * `services` doesn't exists use `items` consequently: Previous to this fix we would not show a more tailored message for when you empty result set was due to a user search rather than an empty result set straight from the backend * Fix `error` > `@error` in ErrorState plus code formatting and more docs * Changelog
CONSUL_NODE_COUNT=0
cookie value to see this on the node listing page)services
is now undefined in our Service List template, we should be usingitems
instead. Consequently our slightly better tailored message wasn't showing at all, with this fix it will. You can see the difference pre and post PR for this one by using the search bar to search for a service that doesn't exist.@
in our ErrorState component, the small consequence of this is when we have an error that specified adetail
property, thedetail
would not show and the error state would use the default text instead. I took the opportunity here to reformat the code slightly in the component, use ourAction
component and improve the docs slightly.