-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Use name component in signature requests #20831
Conversation
Update Lavamoat policies.
Add petnames feature. Add name controller instance.
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. |
Fix linting.
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #20831 +/- ##
===========================================
- Coverage 68.26% 68.25% -0.01%
===========================================
Files 1002 1003 +1
Lines 40133 40151 +18
Branches 10742 10743 +1
===========================================
+ Hits 27395 27402 +7
- Misses 12738 12749 +11
☔ View full report in Codecov by Sentry. |
Builds ready [c5fdaca]
Page Load Metrics (1600 ± 42 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Builds ready [6534103]
Page Load Metrics (1843 ± 88 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Works great for me. 12.mov |
The base branch was changed.
Builds ready [4f56098]
Page Load Metrics (1555 ± 74 ms)
Bundle size diffs
|
Explanation
In the
flask
build type only, use theName
component to display addresses in typed V3 and V4 signature requests.This enables the user to specify custom names for any of the signature request addresses, but also to select from a list of proposed names from multiple sources including ENS, Etherscan, Lens Protocol, and the blockchain itself.
Screenshots
Before
After
Manual Testing Steps
Sign
underSign Typed Data V3
.Sign Typed Data V4
.Pre-merge author checklist
Pre-merge reviewer checklist
If further QA is required (e.g. new feature, complex testing steps, large refactor), add the
Extension QA Board
label.In this case, a QA Engineer approval will be be required.