Feature : Identification for Third Party Commands#68573
Feature : Identification for Third Party Commands#68573Vrishabhsk wants to merge 2 commits intoWordPress:trunkfrom
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
@Vrishabhsk, do you mind rebasing this branch on top of the latest trunk and resolving merge conflicts? |
|
Thanks for the ping! Personally, I think the approach of using the
I believe it's up to the plugin developer whether they want to display the plugin name or not, and for example, plugin developers are free to include their branding in the label using a command like this: useCommands( [
{
name: 'jetpack/activity-log',
label: __( 'Jetpack > Activity log' ),
icon: jetpackIcon1,
},
{
name: 'jetpack/activity-log',
label: __( 'Jetpack > Copy shortlink' ),
icon: jetpackIcon2,
},
] ); |
|
I agree, Instead of plugin name. We should give plugin developer freedom to pick which branding they would like to show end users. |
What?
Why?
How?
plugin nameviacommand.nameplugin nameto12 charactersand showellipsisis greater than12Screenshots or screencast