-
Notifications
You must be signed in to change notification settings - Fork 5.4k
feat: claims-controller integration #37597
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
base: main
Are you sure you want to change the base?
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. |
|
@metamaskbot update-policies |
|
Policies updated. 🧠 Learn how: https://lavamoat.github.io/guides/policy-diff/#what-to-look-for-when-reviewing-a-policy-diff |
✨ Files requiring CODEOWNER review ✨🧩 @MetaMask/extension-devs (5 files, +35 -0)
📜 @MetaMask/policy-reviewers (5 files, +35 -0)
Tip Follow the policy review process outlined in the LavaMoat Policy Review Process doc before expecting an approval from Policy Reviewers. 🔗 @MetaMask/supply-chain (5 files, +35 -0)
|
Builds ready [e9c3d5d]
UI Startup Metrics (1223 ± 92 ms)
📊 Page Load Benchmark ResultsCurrent Commit: 📄 Localhost MetaMask Test DappSamples: 100 Summary
📈 Detailed Results
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
| (claim: Claim) => { | ||
| // add leading zero to claim number if it is less than 1000 | ||
| const claimNumber = claim.claimNumber.toString().padStart(3, '0'); | ||
| const claimNumber = claim.id.toString().padStart(3, '0'); |
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.
did you change the id to be a counter on claims ctrl? because the id is too long to show on UI eg. 05fa245a-1a4d-427a-b4bb-c8d409c05c38
we want to show it like Claims #1... on UI.
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.
okie. Then we can use shortId I guess.
…on' into feat/claims-controller-integration
|
@metamaskbot update-policies |
Builds ready [de391d5]
📊 Page Load Benchmark ResultsCurrent Commit: 📄 Localhost MetaMask Test DappSamples: 100 Summary
📈 Detailed Results
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
|
Policies updated. 🧠 Learn how: https://lavamoat.github.io/guides/policy-diff/#what-to-look-for-when-reviewing-a-policy-diff |
Builds ready [5fb972b]
UI Startup Metrics (1230 ± 109 ms)
📊 Page Load Benchmark ResultsCurrent Commit: 📄 Localhost MetaMask Test DappSamples: 100 Summary
📈 Detailed Results
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Builds ready [bf156d9]
UI Startup Metrics (1250 ± 98 ms)
📊 Page Load Benchmark ResultsCurrent Commit: 📄 Localhost MetaMask Test DappSamples: 100 Summary
📈 Detailed Results
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
| headers: { | ||
| Authorization: `Bearer ${accessToken}`, | ||
| }, | ||
| headers, |
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.
@lwin-kyaw : for multipart request, manually setting Content-Type: multipart/form-data without including boundary led to error "missing boundary" when fetch. You must remove "Content-Type: multipart/form-data" at controller or override it here and let browser add it automatically.
Description
This PR integrates
@metamask/claims-controllerinto extension and added SIWE signature generation for the claim.Changelog
CHANGELOG entry: Added
@metamask/claims-controllerfor shield claimsCHANGELOG entry: Added Claim Signature Generation.
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist