Also removes the unstable build badge, which is kind of redundant since
we will always respect the pattern of keeping the `master` branch stable
enough to be used.
Two Scrutinizer badges were added: code coverage and code quality.
Travis changed to report code coverage to Scrutinizer.
This code is from the PHP source itself. It's required to run
Respect\Validation on hhvm, which lacks the class.
By adding it to the library folder, it's loaded automatically
by our testing routines.
Further documentation should be written, but only after a stable
build for hhvm appears on Travis.
Added DK to iso alpha 2 country code list. Now it is iso compliant
(https://www.iso.org/obp/ui/#search/code). Since this list has now 249
items as per iso.org
Skipping TLD check allows for local domains like "machine.dev",
but the default behavior of the rule still the same: it validates
TLDs, so domains will only be valid (by default) if the TLD is a
valid one.
The signature of rule (using the builder) changes from:
v::domain() // Still works, same behavior as before.
To:
v::domain(false) // Skips TLD check.
Fix#33.
The "Domain" rule now validates domains on "ASCII Compatible Encoding"
[ACE][1] for internationalized domain names (ICANN, 2003).
An excerpt from Wikipedia article:
> If given a label containing at least one non-ASCII character, ToASCII
> will apply the Nameprep algorithm, which converts the label to
> lowercase and performs other normalization, and will then translate the
> result to ASCII using [Punycode][16] before prepending the four-character
> string ["xn--"][17].
[1]: http://wikipedia.org/wiki/Internationalized_domain_name#ToASCII_and_ToUnicode
[16]: http://tools.ietf.org/html/rfc3492
[17]: http://www.atm.tut.fi/list-archive/ietf-announce/msg13572.html
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.
