You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On our project we would like to limit the use of lodash JS functions and use the native .forEach / .map / .filter as much as possible.
I totally understand the rationale behind this rule, which is explained in details here : #98 (comment)
Though, do you think it could be possible to add a configuration option to report the opposite, that is to forbid the use of lodash methods when not used with a shorthand ?
The text was updated successfully, but these errors were encountered:
There are various reasons why one might want a never option for this rule, to forbid the use of unchained lodash methods that have native equivalents. I don't think this plugin should be opinionated about this.
If there is demand for this feature, it's worth accepting a PR for it, right? I could take a stab at this if the maintainers indicate they'd be open to merging it.
Hi.
On our project we would like to limit the use of lodash JS functions and use the native
.forEach
/.map
/.filter
as much as possible.I totally understand the rationale behind this rule, which is explained in details here : #98 (comment)
Though, do you think it could be possible to add a configuration option to report the opposite, that is to forbid the use of lodash methods when not used with a shorthand ?
The text was updated successfully, but these errors were encountered: