Skip to end of metadata
Go to start of metadata

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Zend Framework: Zend_Validate_Postcode_Uk Component Proposal

Proposed Component Name Zend_Validate_Postcode_Uk
Developer Notes http://framework.zend.com/wiki/display/ZFDEV/Zend_Validate_Postcode_Uk
Proposers My Name
Zend Liaison TBD
Revision 1.0 - 1 January 2008: Initial Draft. (wiki revision: 7)

Table of Contents

1. Overview

Zend_Validate_Postcode_Uk is class that will validate UK postcodes. It can be used as a part of form element validation or used stand alon

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

Most requirements take the form of "foo will do ...." or "foo will not support ...", although different words and sentence structure might be used. Adding functionality to your proposal is requirements creep (bad), unless listed below. Discuss major changes with your team first, and then open a "feature improvement" issue against this component.

  • This component will validate provided postcode as valid UK postcode

4. Dependencies on Other Framework Components

  • Zend_Validate
  • Zend_Locale

5. Theory of Operation

This validator has only one function to determine if provided postcode is valid UK postcode

6. Milestones / Tasks

Describe some intermediate state of this component in terms of design notes, additional material added to this page, and / code. Note any significant dependencies here, such as, "Milestone #3 can not be completed until feature Foo has been added to ZF component XYZ." Milestones will be required for acceptance of future proposals. They are not hard, and many times you will only need to think of the first three below.

  • Milestone 1: [DONE]design notes will be published here
  • Milestone 2: Working prototype checked into the incubator supporting use cases #1, #2, ...
  • Milestone 3: Working prototype checked into the incubator supporting use cases #3 and #4.
  • Milestone 4: Unit tests exist, work, and are checked into SVN.
  • Milestone 5: Initial documentation exists.

If a milestone is already done, begin the description with "[DONE]", like this:

  • Milestone #: [DONE] Unit tests ...

7. Class Index

  • Zend_Validate_Postcode_Uk

8. Use Cases

UC-01
UC-02

9. Class Skeletons

]]></ac:plain-text-body></ac:macro>

]]></ac:plain-text-body></ac:macro>

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Sep 02, 2009

    <p>What's the difference between this proposal and the existing Zend_Validate_PostCode component ?</p>

    1. Sep 05, 2009

      <p>Well the only one difference is that client is don't need to know the format of the correct UK postcodes. Of course this component can make an use of Zend_Validate_Postcode.<br />
      Anyway it was only a suggestion just to make life little bit easier.</p>

      1. Sep 05, 2009

        <p>Which format ? You don't need to give a format ?</p>

        <p>I would not know why</p>
        <ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
        $validate = new Zend_Validate_Postcode_Uk();
        ]]></ac:plain-text-body></ac:macro>

        <p>should be simpler for a user than</p>
        <ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
        $validate = new Zend_Validate_PostCode('GB');
        ]]></ac:plain-text-body></ac:macro>

        <p>(note that UK is ukrainian and not great britain)</p>

        1. Sep 05, 2009

          <p>Totally agreed with you.</p>

  2. Sep 05, 2009

    <p>This proposed component would do nothing but replicate existing functionality within ZF. Therefore advising against inclusion.</p>

    <p>Edit: I see 1 usecase + 1 heading of a usecase. Your milestones/tasks mention 4 usecases (and a few dots).</p>

    1. Sep 05, 2009

      <p>Sorry for this proposal. It seems it duplicate content. Totally agree with Thomas (see above).</p>

      <p>Is there any way that I can delete this page?</p>