-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Adding the feedback button on activity panel for the classic product page #35810
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
Conversation
Test Results SummaryCommit SHA: 017fcbb
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. |
ccfe5fd to
e44dc68
Compare
fbbe50b to
3a11101
Compare
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.
Thanks for adding this in to the old experience, Joel! The CES modal is testing well for me and all tracks events work as expected 👍
I'm running into 2 issues (not sure if it's just my env):
- After opening the feedback modal, the "Activity Panel" and "Finish setup" buttons no longer work for me.
- After opening and closing the feedback modal a couple times, the activity panel icon remains highlighted like its active even when the modal is closed.
| }; | ||
|
|
||
| const isProductPage = () => { | ||
| const isProductScreen = () => { |
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.
Don't disagree or feel strongly about this change, but just curious if there are reasons to change this name to encompass more screens.
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 was an off the cuff thought to discern the MVP from the current product UI. Basically I associate the term screen a bit more with the reactified MVP, and page moreso with the current UI.
Not sure if this is just me, and something more explicit might be better. I didn't want to use the term "MVP" since that will soon be obsolete, but open to suggestions.
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.
Basically I associate the term screen a bit more with the reactified MVP, and page moreso with the current UI.
I'm fine with either, though I do know we still refer to some areas as "pages." I guess we should figure out which we like and be consistent, but I'm fine with this change for now.
I didn't want to use the term "MVP" since that will soon be obsolete
Definitely agree with this. We need to name what we want it to be going forward and not something "future-y" since it won't always be.
| { | ||
| action: 'new_product', | ||
| label: __( | ||
| title: __( |
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.
Nice 👍
|
Thanks for the review @joshuatf ! I'd actually seen that behavior, but thought I'd resolved it with my last change. Seems not.
I've noticed that some of the above behavior is preexisting (such as the "preview" button the appearance task), but resolving it in all cases might require a bit more nuance on a case-by-case basis. The change I made in 84635fb I believe will result in the best behavior for this particular instance, although IMO the logic in this component is a little unintuitive and overly complex. Perhaps due to revisit in another issue. One other way to approach this is just using the All that said, I believe everything is resolved! Let me know. |
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.
| }; | ||
|
|
||
| const isProductPage = () => { | ||
| const isProductScreen = () => { |
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.
Basically I associate the term screen a bit more with the reactified MVP, and page moreso with the current UI.
I'm fine with either, though I do know we still refer to some areas as "pages." I guess we should figure out which we like and be consistent, but I'm fine with this change for now.
I didn't want to use the term "MVP" since that will soon be obsolete
Definitely agree with this. We need to name what we want it to be going forward and not something "future-y" since it won't always be.
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.
Testing well! Thanks for fixing the state after feedback submission. This LGTM, but there is a conflict so feel free to ping me if you need another ✅
ba31a27 to
5ea33af
Compare
5ea33af to
017fcbb
Compare
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.
Still testing well! 🚢



Changes proposed in this Pull Request:
Closes #35806 .
How to test the changes in this Pull Request:
Checkout branch.
Navigate to classic product editor. (Menu -> Products -> Add New)
Notice that the Feedback button appears in the header above:

Click the feedback button.
Notice that the icon color changes, and the CES modal is displayed.
Open the console and enable tracks debugging with
localStorage.setItem( 'debug', 'wc-admin:*' );Click "Send" on the modal, and ensure that the
wcadmin_ces_feedbackevent is sent with theproduct_feedbackaction and correct score(s).Other information:
pnpm --filter=<project> changelog add?FOR PR REVIEWER ONLY: