-
Notifications
You must be signed in to change notification settings - Fork 49
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
chore: Solve lint warnings #307
Conversation
@Itzabelli is attempting to deploy a commit to the Yearn Finance Team on Vercel. A member of the Team first needs to authorize it. |
apps/common/components/Header.tsx
Outdated
@@ -92,7 +92,7 @@ function NetworkSelector({networks}: {networks: number[]}): ReactElement { | |||
<div key={safeChainID} className={'relative z-50 mr-4'}> | |||
<Listbox | |||
value={safeChainID} | |||
onChange={async (value: any): Promise<void> => onSwitchChain(value.value)}> | |||
onChange={async (value: number): Promise<void> => onSwitchChain(value)}> |
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.
Unsure about this, it conflicts with https://github.com/yearn/yearn.fi/pull/304/files#diff-110219777e6710fd004b7cacde9e6da2a8eb9d9646ba582321aa88ebc90cdf9eR112
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.
LGTM! Let's revert https://github.com/yearn/yearn.fi/pull/307/files#r1277122053 then we can merge
I reverse the replacement of the 'any' type to the 'number' type, because it conflicts with other changes.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Description
After ran
yarn lint
these errors and warnings are being recorded in the terminal.⛔ error Run autofix to sort these imports! simple-import-sort/imports.
The purpose of this PR is to fix them.
Extra: I removed the unnecessary react import.
Related Issue
N/A
Motivation and Context
The intent of these changes are to solve warnings listed above.
How Has This Been Tested?
After making the changes, I ran
yarn dev
and I ensured that everything appears as expected and I confirmed that the console is not registering the warningsScreenshots (if appropriate):
N/A