-
Notifications
You must be signed in to change notification settings - Fork 316
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: appease linter #990
Conversation
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.
Amazing!!! Thanks so much!
@BlaineHeffron I'm too scared to touch the test conflict 😅 |
3d0f717
to
e53d907
Compare
Addressed @chadoh comments, performed rebase, and then added yarn fmt fixes after the rebase. The main fix applied after the rebase was a dependency cycle involving DEFAULT_TIMEOUT and NULL_ACCOUNT. I moved these to types.ts to fix the issue. |
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.
Looks great, let's get it in fast so we don't need to do it again!
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.
There's so much going on here 😭 but I think I covered all of the bases. I'd feel more comfortable with keeping the WebAuth
stuff unchanged for now for security reasons and reviewing that more carefully in a separate PR that aims to minimize the diff so that we can appropriately evaluate the changes. Could you reset that?
Reverted webauth/utils.ts and addressed the other comments. Should be good to go. |
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.
LFG!
I think you need to merge, @Shaptic! |
A number of fixes to remove the warnings and errors across the src/ directory of the project.
I noticed the
src/.eslintrc.js
files was not actually being used when runningyarn fmt
. Sinceyarn fmt
only runs the linter in thesrc
directory anyway, I just merged thesrc/.eslintrc.js
file with the top level.eslintrc.js
file.Then, I added the settings below to be ignored. These were mostly minor docstring formatting complaints or some other trivial things like having spaces in comments.
I then fixed all other issues. The only logic changes are where functions contained for loops, I used iterators instead (e.g forEach, some, filter, etc). There was one case where I added eslint-ignore comments for a double nested for loop that was a bit more complicated so I just decided to leave it be.
Sometimes there were names prefixed with an underscore, in those cases I just removed the underscore.