Skip to content

UX: Send Flow: Add 'Sent to Contract' warning to new send page#22551

Merged
darkwing merged 17 commits intodevelopfrom
release-send-contract-warning
Jan 24, 2024
Merged

UX: Send Flow: Add 'Sent to Contract' warning to new send page#22551
darkwing merged 17 commits intodevelopfrom
release-send-contract-warning

Conversation

@darkwing
Copy link
Copy Markdown
Contributor

Description

This PR implements the "You're sending to a contract" acknowledgement in the new send flow. This existed in the old send flow.

Related issues

N/A

Manual testing steps

  1. Go to the new send page
  2. As the recipient, paste: 0x514910771af9ca656af840dff83e8264ecf986ca ; this is the $LINK token address
  3. See the warning, note that you cannot submit the send until acknowledgement

Screenshots/Recordings

Before

N/A

After

SCR-20240116-mthm

Pre-merge author checklist

  • I’ve followed MetaMask Coding Standards.
  • I've clearly explained what problem this PR is solving and how it is solved.
  • I've linked related issues
  • I've included manual testing steps
  • I've included screenshots/recordings if applicable
  • I’ve included tests if applicable
  • I’ve documented my code using JSDoc format if applicable
  • I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.
  • I’ve properly set the pull request status:
    • In case it's not yet "ready for review", I've set it to "draft".
    • In case it's "ready for review", I've changed it from "draft" to "non-draft".

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

@darkwing darkwing requested a review from a team as a code owner January 16, 2024 20:20
@github-actions
Copy link
Copy Markdown
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

Copy link
Copy Markdown
Member

@NidhiKJha NidhiKJha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non Blocking: But I think, I understand should not be a link, but a button

Comment on lines +83 to +91
<a
key="contractWarningSupport"
target="_blank"
rel="noopener noreferrer"
className="send__warning-container__link"
href={CONTRACT_ADDRESS_LINK}
>
{t('learnMoreUpperCase')}
</a>,
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: We can use ButtonLink here

@codecov
Copy link
Copy Markdown

codecov bot commented Jan 23, 2024

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (46fb4bb) 68.12% compared to head (304600a) 68.18%.

Files Patch % Lines
...nents/multichain/pages/send/components/content.tsx 57.14% 3 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop   #22551      +/-   ##
===========================================
+ Coverage    68.12%   68.18%   +0.06%     
===========================================
  Files         1087     1087              
  Lines        42653    42664      +11     
  Branches     11349    11353       +4     
===========================================
+ Hits         29056    29087      +31     
+ Misses       13597    13577      -20     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [304600a]
Page Load Metrics (897 ± 29 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint113188135209
domContentLoaded106726157
load79010028976129
domInteractive106726157
Bundle size diffs
  • background: 0 Bytes (0.00%)
  • ui: 1.21 KiB (0.02%)
  • common: 0 Bytes (0.00%)

@darkwing darkwing merged commit 05d2bfd into develop Jan 24, 2024
@darkwing darkwing deleted the release-send-contract-warning branch January 24, 2024 15:38
@github-actions github-actions bot locked and limited conversation to collaborators Jan 24, 2024
@metamaskbot metamaskbot added the release-11.10.0 Issue or pull request that will be included in release 11.10.0 label Jan 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

release-11.10.0 Issue or pull request that will be included in release 11.10.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants