You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Justin Mclean (Commented) (JIRA)" <ji...@apache.org> on 2012/03/21 00:01:38 UTC
[jira] [Commented] (FLEX-29) Existing validator and formatter
classes only validate US and Canadian postcodes
[ https://issues.apache.org/jira/browse/FLEX-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233916#comment-13233916 ]
Justin Mclean commented on FLEX-29:
-----------------------------------
Committed to patches branch. Still an open question to what namespace these components should live in I've gone with http://flex.apache.org/ns for now.
> Existing validator and formatter classes only validate US and Canadian postcodes
> --------------------------------------------------------------------------------
>
> Key: FLEX-29
> URL: https://issues.apache.org/jira/browse/FLEX-29
> Project: Apache Flex
> Issue Type: Improvement
> Reporter: Justin Mclean
> Assignee: Justin Mclean
> Priority: Minor
>
> Despite the Flex SDK having several supported locales it only supports US and Canadian style zip codes. It should provide a more flexible way to validate and format worldwide postcodes.
> I've created PostCodeValidation and PostCodeFormatter classes that solve that very issue.
> The components, tests and example application can be found here:
> http://svn.apache.org/viewvc/incubator/flex/whiteboard/jmclean/validators/src/
> Compared to the existing validators they:
> 1. Supports a wide range of postcode formats both numeric and alpha numeric
> 2. Provide convenience functions to obtain formats for common locales
> 3. Provides a mechanism for user defined validation
> 4. Supports fullwidth characters (as it uses flash.globization classes for string comparisons)
> 5. Easier to extend (although less need to do so as they are more flexible)
> Code has been:
> 1. Reviewed by a couple of people on the list and code has been updated based on those reviews.
> 2. Generates nice ASdocs.
> 3. Working examples has been provided.
> 4. Code is unit tested including fullwidth characters.
> 5. Code is better quality than existing ZipCode validator components (IMO)
> Possibly outstanding.
> There are some architectural changes that could be made but they they would probably have to be made to all Validators.
> The ASDocs could do with a review but certainly reasonable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira