summaryrefslogtreecommitdiff
path: root/tools/eslint/node_modules/xtend/package.json
diff options
context:
space:
mode:
authorRich Trott <rtrott@gmail.com>2017-05-03 21:07:54 -0700
committerMyles Borins <mylesborins@google.com>2017-09-05 12:49:53 -0400
commit688e5ed6fd9aee2ecab576282dfd131db0a4711e (patch)
treec53f866d46319d0f47e8e743dca3163e194ee465 /tools/eslint/node_modules/xtend/package.json
parent40a61e13994761aa91c13a71df97ccba57d33b2b (diff)
downloadnode-new-688e5ed6fd9aee2ecab576282dfd131db0a4711e.tar.gz
test: remove common.noop
This change removes `common.noop` from the Node.js internal testing common module. Over the last few weeks, I've grown to dislike the `common.noop` abstraction. First, new (and experienced) contributors are unaware of it and so it results in a large number of low-value nits on PRs. It also increases the number of things newcomers and infrequent contributors have to be aware of to be effective on the project. Second, it is confusing. Is it a singleton/property or a getter? Which should be expected? This can lead to subtle and hard-to-find bugs. (To my knowledge, none have landed on master. But I also think it's only a matter of time.) Third, the abstraction is low-value in my opinion. What does it really get us? A case could me made that it is without value at all. Lastly, and this is minor, but the abstraction is wordier than not using the abstraction. `common.noop` doesn't save anything over `() => {}`. So, I propose removing it. PR-URL: https://github.com/nodejs/node/pull/12822 Backport-PR-URL: https://github.com/nodejs/node/pull/14174 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Refael Ackermann <refack@gmail.com>
Diffstat (limited to 'tools/eslint/node_modules/xtend/package.json')
0 files changed, 0 insertions, 0 deletions