You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/12/29 21:44:00 UTC

[jira] [Commented] (TAP5-2655) Create annotation to disable validation in event handler methods

    [ https://issues.apache.org/jira/browse/TAP5-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256179#comment-17256179 ] 

ASF subversion and git services commented on TAP5-2655:
-------------------------------------------------------

Commit 9a262668b8333496d0813f3ed519f4014f6616d8 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=9a26266 ]

TAP5-2655: annotation to disable validation in event handler methods

> Create annotation to disable validation in event handler methods
> ----------------------------------------------------------------
>
>                 Key: TAP5-2655
>                 URL: https://issues.apache.org/jira/browse/TAP5-2655
>             Project: Tapestry 5
>          Issue Type: Improvement
>            Reporter: Thiago Henrique De Paula Figueiredo
>            Assignee: Thiago Henrique De Paula Figueiredo
>            Priority: Minor
>
> When an event handler method refers to a non-existent component id, Tapestry throws an exception. In situations with template inheritance and extension points, it's hard or impossible to resolve this problem. A new annotation, @DisableStrictChecks, would be created for disabling this validation for specific methods.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)