Allow string arrays to be received for custom ransacker. #488
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
jonatack
added a commit
that referenced
this pull request
Jan 5, 2015
Allow string arrays to be received for custom ransacker.
|
Great! Thank you. Closes #472. |
jonatack
added a commit
that referenced
this pull request
Jan 6, 2015
jonatack
added a commit
that referenced
this pull request
Jan 14, 2015
This pull request was closed.
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.
This is a fix for the last example in #472 in which filtering on a string field does not work in Arel >= 6. The test written passes with Arel 5 without the fix, and the fix allows the test to pass in Arel 6.