Repository navigation
Components: Refactor withFallbackStyles from class to function component #78837
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
Merged
Mamaduka
merged 4 commits into
WordPress:trunk
from
rushikeshmore:refactor/with-fallback-styles-hooks
Jun 23, 2026
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
8f844e2
Components: Refactor withFallbackStyles from class to function component
rushikeshmore abf270f
Components: Simplify withFallbackStyles per review
rushikeshmore c8c6114
Merge branch 'trunk' of github.com:WordPress/gutenberg into refactor/…
Mamaduka 14da661
Latest feedback
Mamaduka File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
47 changes: 47 additions & 0 deletions
47
packages/components/src/higher-order/with-fallback-styles/test/index.tsx
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| /** | ||
| * External dependencies | ||
| */ | ||
| import { render, screen } from '@testing-library/react'; | ||
|
|
||
| /** | ||
| * Internal dependencies | ||
| */ | ||
| import withFallbackStyles from '..'; | ||
|
|
||
| describe( 'withFallbackStyles', () => { | ||
| const Wrapped = ( props: { fallbackColor?: string } ) => ( | ||
| <div>{ props.fallbackColor ?? 'no-fallback' }</div> | ||
| ); | ||
|
|
||
| it( 'derives the fallback styles from the provided node prop', () => { | ||
| const node = document.createElement( 'span' ); | ||
| node.dataset.color = 'rgb(1, 2, 3)'; | ||
| const mapNodeToProps = jest.fn( ( el: HTMLElement ) => ( { | ||
| fallbackColor: el.dataset.color, | ||
| } ) ); | ||
| const Component = withFallbackStyles( mapNodeToProps )( Wrapped ); | ||
|
|
||
| render( <Component node={ node } /> ); | ||
|
|
||
| // The rendered value proves the actual node was read by mapNodeToProps. | ||
| expect( mapNodeToProps ).toHaveBeenCalledWith( | ||
| node, | ||
| expect.objectContaining( { node } ) | ||
| ); | ||
| expect( screen.getByText( 'rgb(1, 2, 3)' ) ).toBeInTheDocument(); | ||
| } ); | ||
|
|
||
| it( 'derives the fallback styles from the internal wrapper node when no node prop is given', () => { | ||
| const mapNodeToProps = jest.fn( ( el: HTMLElement ) => ( { | ||
| fallbackColor: el.tagName.toLowerCase(), | ||
| } ) ); | ||
| const Component = withFallbackStyles( mapNodeToProps )( Wrapped ); | ||
|
|
||
| render( <Component /> ); | ||
|
|
||
| // The HOC wraps in a <div>, so reading the node's tagName yields 'div'. | ||
| expect( mapNodeToProps ).toHaveBeenCalled(); | ||
| expect( mapNodeToProps.mock.calls[ 0 ][ 0 ].tagName ).toBe( 'DIV' ); | ||
| expect( screen.getByText( 'div' ) ).toBeInTheDocument(); | ||
| } ); | ||
| } ); | ||
Oops, something went wrong.
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.
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.
It would be good to test that the
node, either supplied as a prop or created in the wrapper, can be actually used to derive the styles. At this moment neither of the two tests makes any use of the DOM node.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.
Updated in 9a14a5a. Both tests now read from the real node (
dataseton the provided node,tagNameon the internal wrapper) so they actually exercise the node wiring.