You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Thiago Henrique De Paula Figueiredo (Jira)" <ji...@apache.org> on 2022/05/28 02:47:00 UTC

[jira] [Reopened] (TAP5-2725) Lack of consistency in DateField validation error message

     [ https://issues.apache.org/jira/browse/TAP5-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thiago Henrique De Paula Figueiredo reopened TAP5-2725:
-------------------------------------------------------

Implementation above had to be reverted because it was causing some bad unintended consequences

> 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
>             Fix For: 5.8.2
>
>
> 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)