[jira] [Updated] (TAP5-1104) FieldTracker are not exposed and hence it is difficult to locate the field in error from ValidationTracker

["Ulrich Stärk (JIRA)" <ji...@apache.org>]

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

Ulrich Stärk updated TAP5-1104:
-------------------------------

    Labels: bulk-close-candidate  (was: )

This issue has been last updated more than 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry, please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.
                
> FieldTracker are not exposed and hence it is difficult to locate the field in error from ValidationTracker
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1104
>                 URL: https://issues.apache.org/jira/browse/TAP5-1104
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Jayesh
>              Labels: bulk-close-candidate
>
> I need to provide hyperlinks to the individual fields in errors at the top. 
> Tapestry4 had -> IFieldTracking field = IValidationDelegate.getFieldTracking(); 
> I couldn't find any equivalent in tapestry5. 
> Tapestry 5 validator returns List<String> getErrors(); But then there is no way to link these error messages to the actual fields which are in error. 
> I need to follow company's web standards which mandates to provide <anchor> links to errornous fields, so clicking at the those error texts jumps the user to appropriate label/field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira