I’m happy to present you a new release of assertj-vavr. This version, i.e., v0.1.0, uses Vavr v0.10.0 and adds support of more types from this library.
Below you can find the information about what’s new.
Enhancements:
Maps support
One of the missing parts was a possibility to make assertions on instances ofio.vavr.colleciton.Map. The new version provides basic checks. Among checks of its emptiness, equality, and size, you can run checks for contained entries, keys, and values. Here’s a sample:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Another missing part in the library was assertions for io.vavr.control.Validation. Now, you can check the following:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Another nice-to-have thing is assertions for lazily evaluated values. With the new release, we can check whether a given computation is evaluated or not.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
While io.vavr.control.Try is already supported since the first release, we have added simple checks to see is it a success or a failure.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The recent version of the library fixes a bug of asserting whether value contained by Option/Try/Either is null. While you can use such value in those types, assertj-vavr provided no support for checking this. Now, we have fixed it.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If you have any ideas about what we should add in future releases of the library, let us know (comment below, contact me, create a new issue or catch me on JVM Poland Slack). And, of course, your contribution to the project is more than welcome!
We have just released the 0.2.0 version of the assertj-vavr library. With this release, you get the assertions for Vavr’s Multimap type, a bunch of new ones for Map, the next two for Either, and Read more…
If you are working with Java, you probably know Vavr library, I guess. It is a great library, and it is my default in every Java project I am working on, as it was with Read more…
0 Comments