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

replace: Use object[property] to check if property exists #87

Merged
merged 2 commits into from
Mar 30, 2016

Conversation

Turbo87
Copy link
Contributor

@Turbo87 Turbo87 commented Mar 22, 2016

This PR resolves #86

@searls
Copy link
Member

searls commented Mar 30, 2016

The way this PR changes the behavior, if a property does exist but is falsey, then the error will be raised, which is a breaking change.

The way I see it, we could either avoid making a breaking change by adding the new condition as an ||, or embrace the breaking change and be more specific into what's allowed by type-checking the property and verifying it is either _.isFunction or _.isObject.

@searls searls merged commit b01a99b into testdouble:master Mar 30, 2016
@Turbo87
Copy link
Contributor Author

Turbo87 commented Apr 1, 2016

@searls any chance of a new release in the near future?

@Turbo87 Turbo87 deleted the replace branch April 1, 2016 16:04
@searls
Copy link
Member

searls commented Apr 1, 2016

Yes, sorry for the delay, I've got a few changes in flight that have held me back. I'll release by end of day tomorrow at the latest

@searls
Copy link
Member

searls commented Apr 3, 2016

Hey @Turbo87 this landed last night in 1.3.0, but there was a regression breaking 0.10.x users, so the latest is 1.3.1

@Turbo87
Copy link
Contributor Author

Turbo87 commented Apr 3, 2016

@searls awesome, thanks!

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

Successfully merging this pull request may close these issues.

td.replace() fails for method on prototype
2 participants