-
Notifications
You must be signed in to change notification settings - Fork 541
[common-v2.1.7-alpha.5, core-v2.6.0-alpha.8, react-v2.2.5-alpha.7]fix: weifix #1180
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
Conversation
| Joi.number().positive()).required, | ||
| id: Joi.string() | ||
| .pattern(/^0x[0-9a-fA-F]+$/) | ||
| .required(), |
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.
Any reason to change this validation?
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 was related to the validation error fix for hardware wallets chain added to the main release:
There is another Joi.alternatives- string or number validation included in the previous PR core chainID which .
I guess placing chains: Chain[] | ChainWithDecimalId[] will allow for such validation but I'm not sure that's needed since the GetInterfaceHelpers used by Ledger works with the internal hex string.
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 seem correct if we are using Hex chain IDs internally(converting number chain ids to hex after initialization) it doesn't seem we would need positive number validation within the common package although I may be misunderstanding the possible flows of potential chainId
|
Do we also need to remove the bignumber.js dep from core and the rollup externals since it is not being used anymore? |
It's still used by preflight-notifications.ts and notify.ts |
Description
This PR:
Checklist
package.jsonis incremented following semantic versioningyarn type-check&yarn buildto confirm there are not any associated errors