Handle error message possibly already being an array #5
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
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.
I ran into an issue upgrading dynamic_form on an older application. I think the commit that made the library compatible with newer versions of rails inadvertently removed support for certain kinds of association validations.
It removed the
messages = Array.wrap(messages)casting that handled error messages whether they were already an array or not.I don't have a standalone reproducible example but I wanted to open this PR anyway in case anyone else runs into the same problem.
The diff is much clearer if you hide whitespace (https://github.com/payrollhero/dynamic_form/pull/5/files?diff=unified&w=1).