As the project already is installed via composer, this command
could save a few keystrokes!
Besides that, is just one command for all OS, because will not be
needed to change slashes to backslashes in Windows.
*X (21 keystrokes): `./vendor/bin/phpunit`
Windows (21 keystrokes): `.\vendor\bin\phpunit`
New (14 keystrokes): `composer test`
https://getcomposer.org/doc/articles/scripts.md#writing-custom-commands
Since we are using only composer as autoloader and we have all
dependencies on `require-dev` there is no need to check if third-party
libraries are present or not
The API of Symfony\Component\Validator changed more than 2 years ago, so
this validation rule wasn't working for quite a long time.
This fixes the validator to work with versions >= 2.1 of
Symfony/Validation as the change on composer shows us. Although a bug
fix, this breaks compatibility with people already using this validator.
I was astonished to not find any tests for that validator also. :(
With those tests we can ensure that any change on the component API will
be noticed by us.
We can always use Respect/Foundation, but with that component on
composer.json I think it is easier for new contributors to get things
running on their development environment.
Instead of keeping the file up to date and confusing ourselves with
changes to the file on the version control, the author's not point to
GitHub list of contributors.
And package.ini (although it need more tweeks).
On composer.json I removed the version declaration, since it is taken
from Git Tags (by Packagist) and added keywords to ease the search.
PS: I have a (big and bad) feeling this will break Travis because of
Respect/Foundation.
- Refactor Zend validator tests
- Fixed my email on composer.json
- Added dev packages in composer.json:
- Zend\Validator 2.*
- Symfony\Component\Valitor 2.*
PS: This is just a quick fix before Foundation can run this on his
own.
