-
Notifications
You must be signed in to change notification settings - Fork 219
Remove isExperimentalBuild
Checks in Classic Template Block
#8902
Remove isExperimentalBuild
Checks in Classic Template Block
#8902
Conversation
By removing the `isExperimentalBuild` conditional checks in the Classic Template block, we can ensure the features added in #8324 will land in WooCommerce Core and are not limited to the feature plugin. See p1680000654295729-slack-C02UBB1EPEF for additional context.
The release ZIP for this PR is accessible via:
Script Dependencies ReportThere is no changed script dependency between this branch and trunk. This comment was automatically generated by the TypeScript Errors Report
🎉 🎉 This PR does not introduce new TS errors. |
Size Change: -1 B (0%) Total Size: 1.07 MB
ℹ️ View Unchanged
|
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.
Thank you @danielwrobert for addressing this so quickly. Just tested and it is working as expected, can't see any side-effects, great job! 🚀
The conditional `isExperimentalBuild` conditional check that was wrapping some conditional registration of the classic template block seems to be unrelated to the template conversion/migration. This is something we can revisit and test separately but should not be included in this changeset.
@thealexandrelara I pushed an update in 3ee34d5, if you can have another look when you have a chance - thanks! I also updated the test plan to clarify that you need to run |
* Remove isExperimentalBuild checks. By removing the `isExperimentalBuild` conditional checks in the Classic Template block, we can ensure the features added in #8324 will land in WooCommerce Core and are not limited to the feature plugin. See p1680000654295729-slack-C02UBB1EPEF for additional context. * Revert isExperimentalBuild removal on registration The conditional `isExperimentalBuild` conditional check that was wrapping some conditional registration of the classic template block seems to be unrelated to the template conversion/migration. This is something we can revisit and test separately but should not be included in this changeset.
* Empty commit for release pull request * Add WC Blocks 9.9.0 changelog * Update supported versions for WC Blocks 9.9.0 * Update versions for WC Blocks 9.9.0 * Add testing notes for 9.90 release * Update testing instructions Co-authored-by: Thomas Roberts <5656702+opr@users.noreply.github.com> * Remove active the latest trunk part from the testing instructions Co-authored-by: Thomas Roberts <5656702+opr@users.noreply.github.com> * Add instructions to activate WP release candidates - Add the editor type for each reference. - Add instructions to activate WP release candidate * Fix readme file reference * Fix unlinked border widths in WP 6.2 (#8893) * Check for address on shippingData (#8878) * Make a Single Product conversion enabled in Core, but keep the Product Archive behind experimental flag (#8907) * Remove `isExperimentalBuild` Checks in Classic Template Block (#8902) * Remove isExperimentalBuild checks. By removing the `isExperimentalBuild` conditional checks in the Classic Template block, we can ensure the features added in #8324 will land in WooCommerce Core and are not limited to the feature plugin. See p1680000654295729-slack-C02UBB1EPEF for additional context. * Revert isExperimentalBuild removal on registration The conditional `isExperimentalBuild` conditional check that was wrapping some conditional registration of the classic template block seems to be unrelated to the template conversion/migration. This is something we can revisit and test separately but should not be included in this changeset. * Update changelog and testing instructions to include cherry-picked PRs * Update release zip * Update readme to be in correct order --------- Co-authored-by: github-actions <github-actions@github.com> Co-authored-by: Tarun Vijwani <tarun.vijwani@automattic.com> Co-authored-by: Thomas Roberts <5656702+opr@users.noreply.github.com> Co-authored-by: Albert Juhé Lluveras <contact@albertjuhe.com> Co-authored-by: kmanijak <karol.manijak@automattic.com> Co-authored-by: Daniel W. Robert <danielwrobert@users.noreply.github.com> Co-authored-by: Thomas Roberts <thomas.roberts@automattic.com>
By removing the
isExperimentalBuild
conditional checks in the Classic Template block, we ensure that the capability of switching to the blockified Single Product Template will land in WooCommerce Core and not be limited to the feature plugin.This is an adjustment from #8324. The test plan is the mainly the same, with some minor adjustments.
See p1680000654295729-slack-C02UBB1EPEF for additional context.
Screenshots
Screen.Capture.on.2023-03-23.at.09-43-02.mp4
Testing
Prerequisites:
WordPress: >=6.1
Make sure
Single Product
template customizations are reset to the default state:/wp-admin/site-editor.php?postType=wp_template
)Clear customizations
Steps
npm run build:deploy
).Single Product
template.Upgrade to Blockified Single Product Template
button.WooCommerce Visibility
Changelog