-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Component: Custom Spending Cap #5083
Conversation
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. |
792e758
to
fcd838a
Compare
757dd2a
to
a410dd1
Compare
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.
Found a handful of UI issues and it was easier to just address them rather than commenting in all of the places. I created a branch cal/183-custom-spending
with those changes. Feel free to use that as a reference or you can just pull directly as well.
app/component-library/components-temp/CustomSpendCap/CustomSpendCap.types.ts
Show resolved
Hide resolved
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.
Left some more comments before merging. LGTM after addressing those.
Development & PR Process
release-xx
label to identify the PR slated for a upcoming release (will be used in release discussion)needs-dev-review
label when work is completedneeds-qa
label when dev review is completedQA Passed
label when QA has signed offDescription
This PR is part of the UI improvements for setting transaction spend limit. There is no QA review required at this time as this code is still in its component definition.
Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions,
1. What is the reason for the change?
2. What is the improvement/solution?
Screenshots/Recordings
[Image]
https://user-images.githubusercontent.com/10342624/182721189-32deedf9-3a3b-4046-8f4f-609f4c0da183.png
[Updated Video]
http://recordit.co/5hNgjN11Om
If applicable, add screenshots and/or recordings to visualize the before and after of your change
Issue
Progresses https://github.com/metamask/metamask-planning/issues/183
Checklist