Document grid row state styling change (26.3.8) in breaking changes - #1319
Merged
Conversation
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
2 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.
Since 26.3.8 (commit 35c1076), selectable grid rows take their
hover/cursor/selected/selected-cursorstyles from$cx-grid-data-state-style-mapinstead of$cx-list-item. Projects that customized row appearance through$cx-list-itemlose that styling on grids after upgrading, and previously-ignored entries in the grid map start to apply. Found while upgrading the CxO Admin Portal from 25.6 to 26.8 (CxODEV-1855); verified against published npm tarballs (26.3.7 = old behavior, 26.3.8 = new).This adds a 26.3.8 section to the breaking-changes page with the symptom description and a before/after migration example.