Issues

ZF-2336: Promote Zend_Validate_Barcode and friends to core for release

Description

Once unit testing for each file of the component reaches 80% LOC coverage and there exists satisfactory DocBook documentation for the APIs, the Zend_Validate_Barcode component needs to be promoted to core (i.e., moved to trunk with unit tests and documentation integrated).

Comments

Andries, what is the status of Zend_Validate_Barcode? Should it be included in the preview release?

Wil, everything besides DocBook documentation is done.

Documentation is done, ready to promote to core.

We should have some deterministic method to arrive on constant values used in the {{Zend_Validate_*}} classes. See [ZF-2397] for more information. I'm not sure which approach would be best, but we should pick something. For the short term, I suggest the following:


Zend_Validate_Barcode_UpcA::INVALID = 'invalid';
Zend_Validate_Barcode_UpcA::INVALID_LENGTH = 'invalidLength';
(and similarly for Zend_Validate_Barcode_Ean13)

The questions in my mind are whether or not to "mirror" the constant names with the values, and whether or not to include "namespaces", such as in the following:


Zend_Validate_Barcode_UpcA::INVALID = 'Zend_Validate_Barcode_UpcA::INVALID';

I resolved this in r8210

Fixed for next minor release with SVN r8211.