-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
refactor: move getSelectedInternalAccount
from selectors.js
to accounts.ts
#27644
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. |
Builds ready [cba16ef]
Page Load Metrics (1814 ± 79 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
89f3391
to
6f8f641
Compare
cba16ef
to
3e1f4ed
Compare
6f8f641
to
699334b
Compare
8ac0340
to
23628c4
Compare
getSelectedInternalAccount
from selectors.js
to accounts.ts
getSelectedInternalAccount
from selectors.js
to accounts.ts
699334b
to
c171975
Compare
23628c4
to
88acbfb
Compare
Quality Gate passedIssues Measures |
Builds ready [88acbfb]
Page Load Metrics (1820 ± 119 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
The base branch was changed.
631ebf0
to
a759afc
Compare
Builds ready [a759afc]
Page Load Metrics (2044 ± 215 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
a759afc
to
bb00b2c
Compare
Builds ready [bb00b2c]
Page Load Metrics (2049 ± 118 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
bb00b2c
to
3f2a9e8
Compare
Builds ready [3f2a9e8]
Page Load Metrics (2045 ± 77 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
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.
I have a couple questions related to the @ts-expect-error
exceptions. Otherwise, this looks good to me 👍
@@ -43,6 +43,7 @@ const useBridging = () => { | |||
const isMarketingEnabled = useSelector(getDataCollectionForMarketing); | |||
const providerConfig = useSelector(getProviderConfig); | |||
const keyring = useSelector(getCurrentKeyring); | |||
// @ts-expect-error keyring type is wrong maybe? |
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.
Is this exception expected as part of this refactoring effort?
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.
yes, the existing types used in various places around our codebase don't match what the code actually represents, so we get errors like this when porting from JS to TS. If someone fixes the types this line will cause a compilation error, which is good as it will be the comment should just be removed at that time.
@@ -166,6 +167,7 @@ export function getCustodianIconForAddress(state: State, address: string) { | |||
|
|||
export function getIsCustodianSupportedChain(state: State) { | |||
try { | |||
// @ts-expect-error state types don't match |
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.
Are these exceptions expected as part of this refactoring effort?
No description provided.