Code Quality: Remove deprecated __nextHasNoMarginBottom prop#609
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #609 +/- ##
==========================================
Coverage 73.18% 73.18%
Complexity 1731 1731
==========================================
Files 85 85
Lines 7473 7473
==========================================
Hits 5469 5469
Misses 2004 2004
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
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. |

What, Why, and How?
Removes the usage of the deprecated
__nextHasNoMarginBottomprop as it's the default behavior since WordPress 7.0. The soft deprecation was introduced in WP 6.7 and scheduled to be removed in WP 7.0.Related:
WordPress/gutenberg#73848
WordPress/gutenberg#75139
Use of AI Tools
None
Testing Instructions
Changelog Entry