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

Use returned object in 'function' mode #88

Merged
merged 7 commits into from
Dec 4, 2019
Merged

Conversation

sam97
Copy link
Contributor

@sam97 sam97 commented Nov 29, 2019

When a function is provided as parameter, the return value, if it exists, is used as the new parsedPath. Otherwise, as earlier, the passed parameter is used assuming it has been modified accordingly.

Fixes #85

@yocontra
Copy link
Collaborator

yocontra commented Dec 2, 2019

Can you include a test + doc updates for this change?

README.md Show resolved Hide resolved
@sam97
Copy link
Contributor Author

sam97 commented Dec 4, 2019

I've added another test that I thought would fit, along with some doc changes. Let me know if I've missed anything.

Also let me know if the commits need to be re-arranged or squashed. I'm not aware of the policies.

@yocontra
Copy link
Collaborator

yocontra commented Dec 4, 2019

@sam97 Thanks, I'll publish this as a breaking change since some users may have been relying on the function return value being discarded

@yocontra yocontra merged commit ca50853 into hparra:master Dec 4, 2019
@sam97
Copy link
Contributor Author

sam97 commented Dec 4, 2019

No problem at all! Thanks for the opportunity. :)

Makes sense to play it safe. A suggestion I'd make is that if there are any other breaking changes planned then this could be shelved to ship along with those.

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.

Rename via function. Return object instead of reassign.
2 participants