Refactor: MoreEdit Component to functional React Component#70482
Refactor: MoreEdit Component to functional React Component#70482Mamaduka merged 5 commits intoWordPress:trunkfrom
Conversation
|
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @coderGtm! 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. |
|
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. |
| } | ||
| return ( | ||
| <HorizontalRule | ||
| text={ content } |
There was a problem hiding this comment.
| text={ content } | |
| text={ customText || __( 'Read more' ) } |
There's no need for the state to hold a static fallback value. We can just inline this.
What?
See #22890
This PR refactors MoreEdit component from class based component syntax to newer functional component syntax.
Why?
Class based components are no longer the recommended approach & instead functional syntax with hooks is more recommended
The code becomes more readable & easier to make changes to.
How?
Testing Instructions
I failed to find usages of this component but I maybe wrong. Hence, skipped the Testing and Screenshots section for now.