flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mihai Chira (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-35025) Validator results cannot be intercepted if the value is null
Date Tue, 02 Feb 2016 16:08:39 GMT

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

Mihai Chira updated FLEX-35025:
-------------------------------
    Fix Version/s: Apache Flex 4.16.0

> Validator results cannot be intercepted if the value is null
> ------------------------------------------------------------
>
>                 Key: FLEX-35025
>                 URL: https://issues.apache.org/jira/browse/FLEX-35025
>             Project: Apache Flex
>          Issue Type: Bug
>    Affects Versions: Apache Flex 4.15.0
>            Reporter: Mihai Chira
>            Assignee: Mihai Chira
>             Fix For: Apache Flex 4.16.0
>
>
> {{mx.validators.Validator.validate()}} usually ends up passing its {{ValidationResultEvent}}
through {{handleResults()}}. However, in an edge case (when the value it's validating is {{null}})
it dispatches the {{ValidationResultEvent}} without passing it through {{handleResults()}}.
> The scenario is: we need to set the {{field}} property on the {{ValidationResultEvent}}
before it leaves the custom validator. This is impossible for the (correct) situation when
the value that's being validated is {{null}} (which, in our custom validator, is a valid value).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message