-
-
Notifications
You must be signed in to change notification settings - Fork 208
chore: resolve linting rules | let & const (#281) #282
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
RafaelGSS
left a comment
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.
|
Did you run the banchmark too? |
|
You should not replace |
|
@Eomm Hi, see below for comparative benchmarks using test machineusing let | constvar (master) |
zekth
left a comment
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
zekth
left a comment
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.
Miss this one
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 (I do not see regressions in the benchmarks)
This PR fixes the linting warnings across the codebase to resolve issue #281. It replaces
varforletandconstwhere appropriate.Note: The majority of the replacements were fairly straightforward, however I did spot a possibly
undefinedcondition on line 621 with respect to the variablewalk. You may wish to double check the additionalrefcheck I've added on this code path.Checklist
npm run testandnpm run benchmarkand the Code of conduct