Skip to content

Conversation

@lrcg
Copy link
Contributor

@lrcg lrcg commented Nov 22, 2012

  • invalid field types didn't throw any errors, so errors in schemas, such as alphanum instead of varchar just caused requests to fail (found out the hard way!)
  • reformatted if…else statements to make comparisons between options more easily comparable

lrcg added 3 commits November 22, 2012 23:23
* invalid field types didn't throw any errors, so errors in schemas, such as `alphanum` instead of `varchar` just caused requests to fail (found out the hard way!)
* reformatted `if…else` statements to make comparisons between options more easily comparable
* Reverted `aefdfb0`
* Documented possible design problem with custom datatypes calling
  `parent::validate()` due to the assumptions of `checkLength()` which
  is called by `validate()`
@lrcg
Copy link
Contributor Author

lrcg commented Feb 26, 2013

  • Reverted aefdfb0 because it produces errors whene using a custom datatype
  • Documented possible design problem with custom datatypes calling
    parent::validate() due to the assumptions of checkLength() which
    is called by validate()

@phindmarsh
Copy link
Owner

Check out the validator in https://github.com/wave-framework/wave/tree/master/src/Wave for a (mostly) drop in replacement Validator that is much much more extensible and easier to use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants