Refactor: Use null coalescing operator for improved readability#76777
Refactor: Use null coalescing operator for improved readability#76777
Conversation
|
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @Soean! 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. |
|
Flaky tests detected in e68d7d4. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/23485797781
|
|
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. |
Co-authored-by: Soean <soean@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Co-authored-by: Soean <soean@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
What?
This pull request makes minor improvements to how values are retrieved from arrays in the content guidelines code. The main change is the use of the null coalescing operator (
??) instead of theisset(...)?...:...ternary pattern, which simplifies and modernizes the code.