-
Notifications
You must be signed in to change notification settings - Fork 68
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 Horizontal list of dispute details to the transaction page #7077
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.61 kB (0%) Total Size: 1.41 MB
ℹ️ View Unchanged
|
const columns = [ | ||
{ | ||
title: __( 'Dispute Amount', 'woocommerce-payments' ), | ||
content: formatCurrency( dispute.amount, dispute.currency ), |
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.
IMO we should keep these amounts in the same currency and I believe changing this headline amount is out of scope.
I was looking at updating this as part of #6974 – I agree though, I'll open a separate issue for the headline amount.
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.
Issue #7124 opened and slack discussion about scope here: p1693885409513359-slack-C03LA109BKM
const disputeReason = formatStringValue( | ||
reasons[ dispute.reason ]?.display || dispute.reason | ||
); | ||
const disputeReasonSummary = reasons[ dispute.reason ]?.summary || []; |
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.
Using the summary seems like the best option from the strings file without adding new content.
Closed and re-opened PR to re-trigger the GH checks. |
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 PR tests well @brucealdridge 🏆
I've left some recommended code improvements but these do not block merging, IMO.
I've tested the following:
content={ | ||
<div className="dispute-reason-tooltip"> | ||
<p>{ disputeReason }</p> | ||
<Paragraphs> |
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.
TIL: <Paragraphs />
component exists!
This comment was marked as outdated.
This comment was marked as outdated.
Co-authored-by: Eric Jinks <3147296+Jinksi@users.noreply.github.com>
Co-authored-by: Eric Jinks <3147296+Jinksi@users.noreply.github.com>
Fixes #6924
Fixes #7164
Changes proposed in this Pull Request
A row layout will be added to the DisputeDetails Component showing the key attributes of the dispute. This will show at all times regardless of the status of the dispute.
Dispute Amount
in the store currency. If the store accepts multicurrency payments and the customer paid $70.29 AUD. The amount would be shown as $45.45 USDDisputed On
The date the dispute was opened Reason The reason for the dispute. This includes a ClickTooltip component showing more information about the reason on click.Respond By
The evidence required by date.No details are shown once evidence is submitted or the response date has passed.
Testing instructions
update_option( '_wcpay_feature_dispute_on_transaction_page', '1' );
in WP Console or by modifying your database tablewp_options
directly./wp-admin/admin.php?page=wc-admin&path=%2Fpayments%2Ftransactions%2Fdetails&id=pi_abc&transaction_id=txn_abc&transaction_type=charge
).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