Skip to content
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

Closed
pmcelhaney opened this issue Jul 4, 2016 · 5 comments
Closed

You DO need Lodash #57

pmcelhaney opened this issue Jul 4, 2016 · 5 comments

Comments

@pmcelhaney
Copy link

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.

@cht8687
Copy link
Member

cht8687 commented Jul 4, 2016

I agree with you. As long as we are making developers life easier. 👍

@cht8687
Copy link
Member

cht8687 commented Jul 4, 2016

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

@pmcelhaney
Copy link
Author

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.

@mathieumg
Copy link
Contributor

@stevemao
Copy link
Member

I think https://github.com/wix/eslint-plugin-lodash#preference-over-native provides a good solution for this. Reopen this if you disagree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants