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

Deprecate In methods #166

Open
daedalus28 opened this issue Oct 20, 2017 · 1 comment
Open

Deprecate In methods #166

daedalus28 opened this issue Oct 20, 2017 · 1 comment

Comments

@daedalus28
Copy link
Member

Using _ as a placeholder obviates the need for the In method conversions, because they only save a single character at the cost of new things to learn:

F.someMethodIn(x) vs
_.someMethod(_, x)

Additionally, sometimes our conversion methods would be useful together, e.g. an In and an On. A good example is unset - you might want to unset both in and on an object, and defining compound conversion conventions seems messy (unsetIon?).

In order to make this work, we either need to explicitly curry all our conversions, or wait for lodash/lodash#3440 to be fixed

@daedalus28
Copy link
Member Author

lodash/lodash#3440 is fixed 😄

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

1 participant