Allow to access record value, filled by user in form/API, to be exposed in validation messages #201
Conversation
This file contains hidden or 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
…ed in validation messages
|
I like this idea and wish it was in all attribute level validations. Is there any precedent of this anywhere else? |
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.
Hello, @adzap ! 👋
This PR has the goal to allows access record value, filled by user in form/API, to be exposed in validation messages 👍
Let me know your thoughts about it. I can provide later, once merged, this value in gem documentation and in timeliness-i18n gem ( https://github.com/pedrofurtado/timeliness-i18n ).
c/c: @marciojg 🤝 🤓