-
Notifications
You must be signed in to change notification settings - Fork 69
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 payment activity widget emoji survey #8506
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: +1.56 kB (0%) Total Size: 1.25 MB
ℹ️ View Unchanged
|
Thanks @nagpai 🙌
I also see these warnings, but also on other https://dev-mc.a8c.com/marketing/survey/ screens unrelated to this PR. I'll investigate to see if they are being introduced by this PR. Update: Confirmed that these are harmless warnings and not introduced by this PR. Comparing another survey results page on dev-mc shows the same warnings, but mc works without warnings or problems. ✅
Yes this is caused by test data that was added during development of this feature. We could clean up the |
Thanks so much for checking this! Glad to know it wasn't my setup. Indeed I did see the same warnings with other surveys too, when I checked. 👍 I will do a round of code review today. |
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.
One non-blocking comment on CSS. Rest looks good to go. Thanks!
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.
Great PR @Jinksi 🎉 , looks good to me. Left some comments none of which are blocker for the merge.
Ps: There are some conflicts after merging the data PR.
|
||
type ContextValue = ReturnType< typeof useContextValue >; | ||
|
||
const WcPayOverviewSurveyContext = createContext< ContextValue | null >( null ); |
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.
Love the implementation 🙌 though I am curious about the use of context for this feature, would love to know your thought process here.
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 all carried over from the previous PR #8309. My thought process is that the Context approach works well, so there is no need to change it 😆
Investigating failing GH checks...
|
Fixes #8485
Note
Based on @dpaun1985's PR #8309 – commits have been cherry-picked to this branch.
Changes proposed in this Pull Request
Emoji-based survey component to capture the user sentiment for the new Payments Overview Widget.
The survey accepts 3 fields:
rating
: 'very-unhappy', 'unhappy', 'neutral', 'happy', 'very-happy'comments
: user-defined textwcpay-version
: WooPayments plugin version as text (e.g.7.4.0
)iOS screenshots
Todo
Testing instructions
wp option update _wcpay_feature_payment_overview_widget 1
in CLI (npm run cli
if docker)public-api.wordpress.com
anddev-mc.a8c.com
to your sandbox's IP address if you didn't alreadyarc patch D140691
)Payments -> Overview
wp option delete wcpay_survey_payment_overview_submitted
to clear your local submission stateMJ5lCh.mp4
npm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge