-
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 Overview Widget data highlight components #8303
base: develop
Are you sure you want to change the base?
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: 0 B Total Size: 1.27 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.
LGTM. Tested and works well - I left some minor comments to take a look at but then happy to approve. Thanks for working on it!
|
||
const PaymentChangeFlow: React.FunctionComponent< { | ||
change: number; | ||
} > = ( { change } ): JSX.Element => { |
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.
Since both cases look pretty similar (only some minor class name changes), I wonder if we can just set some variables representing the class names which need to change based on if change < 0
to avoid having to write the markup twice. 🙂
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, @dmallory42! Indeed, that block could be enhanced to avoid duplicate markup. Improved with f9f641b.
change={ 11 } | ||
reportUrl="#" | ||
tooltip={ __( | ||
'Fees includes fees on payments as well as dusputes.', |
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.
Typo: should read disputes
.
Also maybe we should look again at this sentence (I'm not sure if the text has been reviewed yet so please ignore if that's already in progress), using the word 'fees' twice in this sentence may be confusing for merchants IMO.
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! The tooltips are temporary placeholders, as they have not been finalized yet.
Handover details: pepjwh-Ok-p2#comment-931 |
Fixes #8196
Changes proposed in this Pull Request
This PR adds a four column widget to display charges, refunds, disputes, and fees data - based on the selected filters.
Demo:
Overview.Payments.WooCommerce.Payments.WooCommerce.-.6.March.2024.mp4
Testing instructions
Note
Since the Payment Overview Widget data hasn't been implemented yet, we're unable to perform manual testing on the component. Therefore, I've utilized test data for evaluation purposes.
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