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

_.drop not working in 0.7 pre #67

Closed
klimashkin opened this issue Sep 7, 2012 · 6 comments
Closed

_.drop not working in 0.7 pre #67

klimashkin opened this issue Sep 7, 2012 · 6 comments
Labels

Comments

@klimashkin
Copy link

I think you should know :)

_.drop({ 'name': 'moe', 'age': 40, 'userid': 'moe1' }, 'userid');

returns: []

@shanimal
Copy link

shanimal commented Sep 7, 2012

Something is wrong I get an object with name and age...

JSON.stringify(_.drop({ 'name': 'moe', 'age': 40, 'userid': 'moe1' }, 'userid'))
"{"name":"moe","age":40}"

On Sep 7, 2012, at 9:39 AM, klimashkin wrote:

_.drop({ 'name': 'moe', 'age': 40, 'userid': 'moe1' }, 'userid');

@shanimal
Copy link

shanimal commented Sep 7, 2012

Sorry, comprehension fail... different version.

@jdalton
Copy link
Member

jdalton commented Sep 7, 2012

@klimashkin In 0.7 _.drop was moved to _.omit and _.drop became an alias of _.rest for compatibility with Underscore.Next. The compat notes of _.zipObject -> _.object and _.drop -> _.omit and alaising _.rest as _.drop will be made clear in the change log.

@jdalton jdalton closed this as completed Sep 7, 2012
@jdalton
Copy link
Member

jdalton commented Sep 7, 2012

For 0.7.0 docs see https://github.com/bestiejs/lodash/tree/master/doc
and for 0.6.1 see http://lodash.com/docs

@jdalton
Copy link
Member

jdalton commented Sep 7, 2012

Hopefully these changes will be minimal, it's the price we pay for early adoption. However, I would rather get features in than wait for Underscore to settle on an API as it's been almost 6 months since their last stable release.

@lock
Copy link

lock bot commented Jan 21, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

No branches or pull requests

3 participants