-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
lib: replace legacy uses of __defineGetter__ #6768
Conversation
Minor clean up. There are still some places in core that use the legacy __defineGetter__ syntax. This updates those.
@Trott ... is there an eslint rule that can catch these? |
Not a pre-existing one, but I've made a custom one: #6774 According to that lint rule, there are two files missed in this PR:
I can do them as part of that PR or you can add them to this one. Doesn't matter to me either way. |
I have a separate pr that covers the stdio ones. I intentionally did not touch the tests. |
@Trott ... does this PR LGTY? |
LGTM |
Minor clean up. There are still some places in core that use the legacy __defineGetter__ syntax. This updates most of those. PR-URL: #6768 Reviewed-By: Rich Trott <rtrott@gmail.com>
Landed in f293d0b |
Minor clean up. There are still some places in core that use the legacy __defineGetter__ syntax. This updates most of those. PR-URL: #6768 Reviewed-By: Rich Trott <rtrott@gmail.com>
PR-URL: nodejs#6774 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Refs: nodejs#6768
@jasnell lts? |
@thealphanerd Little value; I wouldn't bother. |
Checklist
Affected core subsystem(s)
crypto, readline, internal
Description of change
Minor clean up. There are still some places in core that use the legacy
__defineGetter__
syntax. This updates those.