[EuiBasicTable & EuiInMemoryTable] Fix missing i18n token for default noItemsMessage#5242
Merged
cee-chen merged 3 commits intoelastic:masterfrom Oct 5, 2021
Merged
Conversation
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_5242/ |
thompsongl
approved these changes
Oct 5, 2021
ym
pushed a commit
to ym/eui
that referenced
this pull request
Oct 29, 2021
… noItemsMessage (elastic#5242) * Fix missing i18n token on default empty table message * Update snapshots * Add changelog entry
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Summary
I was messing around EuiBasicTable fixing accessibility issues and noticed this small missing i18n token 👀
QA
asdfasdfand confirm you still see "No items found"Checklist
- [ ] Check against all themes for compatibility in both light and dark modes- [ ] Checked in mobile- [ ] Checked in Chrome, Safari, Edge, and Firefox- [ ] Props have proper autodocs and playground toggles- [ ] Added documentation- [ ] Checked Code Sandbox works for any docs examples- [ ] Added or updated jest tests- [ ] Checked for breaking changes and labeled appropriately- [ ] Checked for accessibility including keyboard-only and screenreader modes