Version 0.2.0

[neocotic]

Here's a summary of the changes for 0.2.0:

• Drop support for Java 7 Drop support for Java 7 #9 (breaking change)
• Support nested arrays and circular references in DefaultArrayFormatter Support nested arrays and circular references in DefaultArrayFormatter #10
• Support different locales Support different locales #11 (breaking change)
• Support multiple verification reporters Support multiple reporters (Take 2) #14 (breaking change)
• Add ClassVerifier#assignableFromAll & ClassVerifier#assignableFromAny Add ClassVerifier#assignableFromAll & ClassVerifier#assignableFromAny #15
• Rename ClassVerifier#interfacing to ClassVerifier#interfaced Rename ClassVerifier#interfacing to ClassVerifier#interfaced #16 (breaking change)
• Rename LocaleVerifier#defaulting to LocaleVerifier#defaulted Rename LocaleVerifier#defaulting to LocaleVerifier#defaulted #17 (breaking change)
• Add StringVerifier#matchAll & StringVerifier#matchAny Add StringVerifier#matchAll & StringVerifier#matchAny #18
• Add ThrowableVerifier#causedByAll & ThrowableVerifier#causedByAny Add ThrowableVerifier#causedByAll & ThrowableVerifier#causedByAny #19
• Add more formatters Add more formatters #21
• Add CustomVerifier#and & CustomVerifier#andComparable methods to allow even more fluid chaining Add CustomVerifier#and & CustomVerifier#andComparable methods to allow even more fluid chaining #22
• Add translations badge to README via Crowdin
• Add JavaDoc badge to README via JavaDoc
• Add code coverage badge to README via Codecov
• Add changelog

[neocotic]

I will also want to make sure that I add a changelog to the project and also update the copyright year for all files to 2017.

[neocotic]

I want to experiment with benchmarking/profiling the new Services stuff as I want to make sure that using SPI won't incur a big performance hit. If it does, I'll consider implementing caching for SPI lookups and/or use-case specific caching.

[neocotic]

I might also add the ability to further chain verifications on to the back of each other by adding and methods to CustomVerifier that provide a similar API to that of Verifier, except that they create a modified copy of the current Verification to avoid additional SPI lookups.

Here's what it could look like, based on the example in the README:

package com.example.form;

import io.skelp.verifier.Verifier;

public class LoginForm implements Form {

    UserService userService;

    @Override
    public void handle(Map<String, String> data) {
        Verifier.verify(data)
            .containAllKeys("username", "password");
            .and(data.get("username"), "username")
                .not().blank();
            .and(data.get("password"), "password")
                .not().empty()
                .alphanumeric();

        userService.login(data);
    }
}

The only thing is that this would obviously only be able to chain built-in verifiers and match the API of our Verifier. I think that this is acceptable though.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@f5a86df). Click here to learn what that means.

@@           Coverage Diff           @@
##             master     #8   +/-   ##
=======================================
  Coverage          ?   100%           
  Complexity        ?   1013           
=======================================
  Files             ?     54           
  Lines             ?   1629           
  Branches          ?    222           
=======================================
  Hits              ?   1629           
  Misses            ?      0           
  Partials          ?      0

Impacted Files	Coverage Δ	Complexity Δ
...main/java/io/skelp/verifier/VerifierException.java	100% <ø> (ø)	4 <ø> (?)
...ava/io/skelp/verifier/type/CollectionVerifier.java	100% <ø> (ø)	3 <ø> (?)
...ain/java/io/skelp/verifier/type/ArrayVerifier.java	100% <ø> (ø)	7 <ø> (?)
.../java/io/skelp/verifier/type/CalendarVerifier.java	100% <ø> (ø)	2 <ø> (?)
...in/java/io/skelp/verifier/type/ObjectVerifier.java	100% <ø> (ø)	1 <ø> (?)
...ava/io/skelp/verifier/type/ComparableVerifier.java	100% <ø> (ø)	1 <ø> (?)
...main/java/io/skelp/verifier/type/DateVerifier.java	100% <ø> (ø)	3 <ø> (?)
...ain/java/io/skelp/verifier/type/ShortVerifier.java	100% <100%> (ø)	25 <ø> (?)
...elp/verifier/type/base/BaseCollectionVerifier.java	100% <100%> (ø)	25 <6> (?)
...elp/verifier/service/ServiceNotFoundException.java	100% <100%> (ø)	1 <1> (?)
... and 44 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f5a86df...d467ae9. Read the comment docs.