dry-validation i18n error full messages user friendly format

The key for the field is always added to the full message and no way to make the key human readable that I can figure out. If there is a way to not have the key in the full error message or allow the ability to format it would be great for UI front end. Maybe, I’m missing something, but the docs show no way to exclude the key or override the default behavior. The default behavior is maybe great for a json API, but not so for a html app. It can read like a developer’s app and not human readable message.
For example:
”some_very_long_variable must be filled” would look better in a flash message as “Must provide a some very long variable” or the ablility to titleize it or humanize it. All of which the basic AR errors provide in a i18n config. Another example is how devise handles error messages in a i18n yaml.

Again, appologies, if this is possible, but I found nothing in the docs and I keep getting this type of thing on full message predicates:
{ player_count: [“player_count Must provide a player count”] }

simple example, but I can see where an attribute could be an abbreviated acronym or really long and you’d like to override this default behavior.
Seems to me there should be a richer way of allowing the developer to make the messages more user friendly and not an auto generated dictation

@gditrick I noticed you cleared out your question (I’ve restored it now). Is this because you found a solution? If so, I’d love it if you could share your solution here! Otherwise I’d be very happy to use this as the basis for a feature request.