-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Support enabling custom link color from theme.json #25148
Merged
Merged
Changes from all commits
Commits
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 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 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 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 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 |
---|---|---|
|
@@ -29,6 +29,7 @@ import { | |
} from '../components/gradients'; | ||
import { cleanEmptyObject } from './utils'; | ||
import ColorPanel from './color-panel'; | ||
import useEditorFeature from '../components/use-editor-feature'; | ||
|
||
export const COLOR_SUPPORT_KEY = '__experimentalColor'; | ||
|
||
|
@@ -181,12 +182,10 @@ const getLinkColorFromAttributeValue = ( colors, value ) => { | |
*/ | ||
export function ColorEdit( props ) { | ||
const { name: blockName, attributes } = props; | ||
const { colors, gradients, __experimentalEnableLinkColor } = useSelect( | ||
( select ) => { | ||
return select( 'core/block-editor' ).getSettings(); | ||
}, | ||
[] | ||
); | ||
const isLinkColorEnabled = useEditorFeature( 'color.link' ); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I really like how the |
||
const { colors, gradients } = useSelect( ( select ) => { | ||
return select( 'core/block-editor' ).getSettings(); | ||
}, [] ); | ||
|
||
// Shouldn't be needed but right now the ColorGradientsPanel | ||
// can trigger both onChangeColor and onChangeBackground | ||
|
@@ -315,8 +314,7 @@ export function ColorEdit( props ) { | |
? onChangeGradient | ||
: undefined, | ||
}, | ||
...( __experimentalEnableLinkColor && | ||
hasLinkColorSupport( blockName ) | ||
...( isLinkColorEnabled && hasLinkColorSupport( blockName ) | ||
? [ | ||
{ | ||
label: __( 'Link Color' ), | ||
|
This file contains 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
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.
maybe there's a better path here?
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.
I'm happy to approve as it is. In its current shape, the other option I can think of is making link a top-level element of
features
, which doesn't feel great either.I also wonder if we should do a follow-up PR when we revisit/consolidate the
features
shape before releasing Gutenberg 9.0. I believe is the first release we include this feature and it'll be good to avoid changing shape later. Left some comments at #20588 (comment)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.
We definitely need a follow-up PR to reshape the paths. That said, I'm not sure if it's before or after Gutenberg 9.0. The important thing is to do it before we make theme.json stable.
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's not the first release for these things, 8.9 include one or two features and dropCap is there for a long time.