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
You DO need Lodash #57
Comments
I agree with you. As long as we are making developers life easier. 👍 |
So in this case, our plugin is dynamic, can be configured to either alternatives => Lodash or Lodash => alternatives, is that what you are suggesting? @pmcelhaney |
Yes. What I like about this repo is it educates me on the advantages and drawbacks of using a library like Underscore, et. al. Using a linter helped me get up to speed with ES6 very quickly. I'm keenly interested in the synergy between linting and learning. |
I think https://github.com/wix/eslint-plugin-lodash#preference-over-native provides a good solution for this. Reopen this if you disagree. |
As @stevemao and others have brought to my attention, there are cases where Lodash provides advantages over the native library. They can provide more consistency across implementations, better performance in typical real world use, or both.
Therefore I think the ESLint plugin should provide options to encourage changing native functions to _ equivalents. Similar to how the no-semi rule provides options to either require semicolons or disallow them.
The text was updated successfully, but these errors were encountered: