Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Message-ID: <1057603121.1246385807209.JavaMail.jira@brutus>
Date: Tue, 30 Jun 2009 11:16:47 -0700 (PDT)
From: "Howard M. Lewis Ship (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Subject: [jira] Created: (TAP5-760) The Form event "validateForm" is
 awkward, a new name (perhaps "formValidate") would be nice
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

The Form event "validateForm" is awkward, a new name (perhaps "formValidate") would be nice
-------------------------------------------------------------------------------------------

                 Key: TAP5-760
                 URL: https://issues.apache.org/jira/browse/TAP5-760
             Project: Tapestry 5
          Issue Type: Improvement
          Components: tapestry-core
    Affects Versions: 5.1.0.5
            Reporter: Howard M. Lewis Ship
            Priority: Minor


You end up with methods like onValidateFormFromLogin() which is just asking for trouble.

onFormValidateFromLogin() is a bit better.

Obviously, we keep the old name as well ... have to fire two events at the validate form stage.

What would be a better name?  Something that doesn't have "form" is it; perhaps "finalValidation" or just "validate". I remember this was a problem with calling it "validate" before, because this conflicted with the validate event form form control element components ... but is that really a problem?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.