Do not try to coerce "" for numeric & date params #1
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.
Description
When using an HTML form for searching or filtering and a field is left blank, Rails puts an empty string in the params hash, and this raised an unexpected
InvalidParameterError
when we defined the param as a non-required Integer, Float, Date, etc.Now we will treat that empty string as an un-supplied param and only reject it if the param is flagged as required.
Additional Notes
I suggested this improvement for the
rails_param
gem over a year ago (nicolasblanco#103) - the maintainers mistakenly thought this was a breaking change for JSON APIs and declined to provide an example.