[EuiBasicTable] Always use Column Index for Footer key#3559
Merged
pickypg merged 3 commits intoelastic:masterfrom Jun 4, 2020
Merged
[EuiBasicTable] Always use Column Index for Footer key#3559pickypg merged 3 commits intoelastic:masterfrom
pickypg merged 3 commits intoelastic:masterfrom
Conversation
This forces all keys to be unique regardless of field name collisions and computed columns.
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_3559/ |
Co-authored-by: Caroline Horn <549577+cchaos@users.noreply.github.com>
Member
Author
|
@cchaos Good catch (and better phrasing on the changelog). |
cchaos
approved these changes
Jun 4, 2020
Contributor
cchaos
left a comment
There was a problem hiding this comment.
👍 If CI passes, good to merge!
|
Preview documentation changes for this PR: https://eui.elastic.co/pr_3559/ |
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
3 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
This forces all keys to be unique regardless of field name collisions (rare) and computed columns (less rare).
Closes #3558
Checklist
[ ] Check against all themes for compatibility in both light and dark modes[ ] Checked in mobile[ ] Checked in IE11 and Firefox[ ] Props have proper autodocs[ ] Checked for breaking changes and labeled appropriately[ ] Checked for accessibility including keyboard-only and screenreader modes