Don't remove parameters with empty values. #47
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sometimes things need to be set to nil or an empty string.
|
👍 |
mwunsch
added a commit
that referenced
this pull request
Jun 11, 2015
Don't remove parameters with empty values.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes things need to be set to nil or an empty string.
In our case we're using Weary to update a central user database. Somebody who loses a job for instance has to have their title and department changed to nil or an empty string. But these params were being removed.
I can't think of any reason empty params should be removed and all the tests passed without the code that removes them so it seems like there's no reason to have that functionality.