-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Add advanced setting option #36380
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 advanced setting option #36380
Conversation
Test Results SummaryCommit SHA: 347b553
To view the full API test report, click here. To view the full E2E test report, click here. To view all test reports, visit the WooCommerce Test Reports Dashboard. |
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.
Looks great and the toggle is working well! My tooltip HTML is coming out escaped though. Is there another branch or some setting needed for this to work?
Additionally, the warning from the other plugins being active prevents activation of the feature. This does not need to be tackled in this PR, but seems a little opinionated and prevents us from using features as intended to roll out experimental features.
cc @Konamiman if you have more context around those decisions.
|
Hi @octaedro and @joshuatf. There's a legacy features array in the class: This warning exists to keep site admins informed about the declared compatibility of other plugins with newly introduced WooCommerce features. Maybe this could be selectively disabled by adding a new flag in the features array that is generated in the constructor, but as you said that would be a job for a different pull request. |
a5075db to
039ff46
Compare
|
Thank you @Konamiman and @joshuatf for your answers. I just addressed the changes you mentioned. @joshuatf Could you take another look at this PR? |
joshuatf
left a 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.
This is testing well for me and LGTM, thanks for the changes, @octaedro!
Thanks for the insight, @Konamiman! I think we might look into either making the compatibility catches opt-in or at least changing the terms legacy so that we can ship new features without risk of them being unusable.
@octaedro do you want to create a follow-up issue around that or would you like me to?
joshuatf
left a 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.
LGTM! Nice work getting those e2e tests fixed up 🎉
| ?> | ||
| <tr valign="top" class="<?php echo esc_attr( implode( ' ', $visibility_class ) ); ?>"> | ||
| <th scope="row" class="titledesc"><?php echo esc_html( $value['title'] ); ?></th> | ||
| <td class="help-tooltip"><?php echo isset( $value['tooltip'] ) && '' !== $value['tooltip'] ? wc_help_tip( esc_html( $value['tooltip'] ) ) : ''; ?></td> |
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.
Interestingly, this new cell creates an issue on the WooCommerce ▸ Settings ▸ Advanced ▸ Custom Data Stores screen, effectively displacing some other settings (because the rows above and below contain just two table cells):
I haven't had a chance to look in any depth—I just noticed while working on some HPOS stuff—but I wonder if this is causing a problem on other screens, too (and/or what the best solution is).
cc @octaedro
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.
Thank you @barryhughes for reporting this.
I just created a PR to fix that.



All Submissions:
Changes proposed in this Pull Request:
This PR adds a new setting in
Settings>Advanced>Features.The setting should be disabled by default unless it was enabled through the flows described in #36161 and #36162
Include a tooltip to describe the new exp briefly.
Closes #36163.
How to test the changes in this Pull Request:
Go to
WooCommerce>Settings>Advanced>Features.Verify the option

New product editoris available to toggle. The description is: "Try the new product editor (Beta)" and the tooltip text says: "Enable to try the new, simplified product editor (currently in development and only available for simple products). No extension support yet."Enable the
New product editorand verify that the new experience is turned on.Verify that the toggle works correctly.
Other information:
pnpm --filter=<project> changelog add?FOR PR REVIEWER ONLY: