-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Add Inline comment experimental flag #60622
base: trunk
Are you sure you want to change the base?
Add Inline comment experimental flag #60622
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @akashdhawade1991, @juhibhatt19. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. 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. |
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @poojabhimani12! In case you missed it, we'd love to have you join us in our Slack community. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
Experimental block commenting
Try/inline block commenting
The following is a summary of the discussion that was had with @ellatrix, that's being posted by me for posterity. In order to be able to test this feature end to end, this PR would need to be updated to add the ability to save comments as well. As a result, the following will need to be be done as the next steps:
|
Addressed feedback
…ltidots/gutenberg into try/inline-block-commenting
…enting Address Rest API Feedbacks
…enting comment rest api function in condition
'gutenberg-experiments', | ||
'gutenberg_experiments_section', | ||
array( | ||
'label' => __( 'Enable multi-user commenting on blocks', 'gutenberg' ), |
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.
This should say something about being internal or for collaborators.
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’ve made this update based on the feedback provided here: #60622 (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.
I'm happy to defer to Matías if he has suggestions. Perhaps: "Enable collaborative commenting on blocks."?
Fix reply comment issue
Here are the details for the split PRs:
|
Remove comment icon
…enting update comment icon code for menu and toolbar group
Sync with trunk
I have moved all the code from the "block-editor" package to the "editor" package. |
|
||
<__unstableCommentIconFill.Slot | ||
fillProps={ { onClose } } | ||
/> |
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.
Do we really need another slot, we already have BlockSettingsMenuControls
or __unstableBlockSettingsMenuFirstItem
in this menu already. Can we use one of these?
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.
Based on feedback, we've added a new slot to display the comment icon below the "Add after" option. If we use the __unstableBlockSettingsMenuFirstItem
slot, the comment icon will instead appear at the top of the menu group.
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 know, how important the position is. Can it be at the top or at the end of the menu instead ?
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.
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.
return $response; | ||
} | ||
add_filter( 'rest_prepare_comment', 'add_user_avatar_urls_in_rest_response_6_7', 10, 1 ); | ||
} |
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 didn't see this in the REST API PR #65181, is it not relevant there?
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.
@@ -34,6 +34,7 @@ | |||
"@babel/runtime": "^7.16.0", | |||
"@wordpress/a11y": "file:../a11y", | |||
"@wordpress/api-fetch": "file:../api-fetch", | |||
"@wordpress/autop": "^4.7.0", |
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.
Why do we need this? This is a sort of legacy package that should be avoided. I don't understand why it's needed.
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.
Based on feedback, we have added this package.
…enting sync rest-api file with api PR
What?
Introducing the "Block Comment" experiment, with added functionality accessible via this feature flag which when enabled, allows users to add comments to the selected block by clicking on "comment" icon in the toolbar dropdown.
Why?
#59445
How?
Testing Instructions
Screenshots or screencast
demo.webm