[
https://issues.apache.org/jira/browse/TAP5-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543059#comment-17543059
]
ASF subversion and git services commented on TAP5-2725:
-------------------------------------------------------
Commit e65243cbab05f177ef9412f4b2ef6e7f5b69a042 in tapestry-5's branch
refs/heads/master from Thiago H. de Paula Figueiredo
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=e65243cba ]
TAP5-2725: Lack of consistency in DateField validation error message
> Lack of consistency in DateField validation error message
> ---------------------------------------------------------
>
> Key: TAP5-2725
> URL: https://issues.apache.org/jira/browse/TAP5-2725
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Reporter: Thiago Henrique De Paula Figueiredo
> Assignee: Thiago Henrique De Paula Figueiredo
> Priority: Major
>
> For almost all, if not all, validation error messages from Tapestry form
> field components, the value isn't shown, just the field name. DateField shows
> the value, so it must be changed to be consistent with the others.
> Notice this changes how the {{core-date-value-not-parseable}} message is
> used. The en, es, fr, it and pt_BR localizations were already updated in this
> ticket.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
