-
-
Notifications
You must be signed in to change notification settings - Fork 30
Fix: arrow function scope strictness (take 2) #52
Fix: arrow function scope strictness (take 2) #52
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.
Thank you for your contribution!
Largely LGTM, but I have a small suggestion.
Would you modify it?
Co-authored-by: Toru Nagashima <star.ctor@gmail.com>
e378bec
to
d801737
Compare
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, thanks! (Would like to get feedback from mysticatea and maybe other team members before merging.)
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, thank you!
I also confirmed that ESLint tests passed.
Can this PR be merged at this point? Or do we need some more reviews? |
Seems mergeable to me. We should plan to do another |
Thanks! |
Fixes #49
This has the original (broken) commit from #50 cherry-picked, and a separate a4ee79e commit fixing the
.length
error from #51.I found linking (
npm link
)eslint-scope
intoeslint
and running eslint's unit tests helpful, maybe this could be part of theeslint-scope
's CI checks?