chore: fix error serialization for string errors #2
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.
When adding custom validation errors, Rails allows both Symbols and Strings:
The Symbol error will later be translated by Rails using the i18n logic, when calling
foo.errors.full_messagesor similar methods. The String error will stay as it is.see https://api.rubyonrails.org/v7.0.8.7/classes/ActiveModel/Errors.html#method-i-add
This commit introduces support for these String errors in the error serialization class.
Before this change, the error response for the validation that was added in the specs looked like this:
Please note the "translation missing" part in the
detail, and thecodethat is a parameterized version of the String error.After this change, the error response looks like this:
The
detailis now the String error as passed in by Rails, and thecodeis a generic"invalid"one.