Closed sweiler closed 7 years ago
@sweiler I appologize for late reply. I really like the names and I will incorporate them as a replacement for current methods. I am wondering if I should bump up the version number (breaking changes) and release it or just deprecate the previous methods and incorporate these methods as replacement for previous methods. Any suggestions?
No worries @npathai :) I would prefer the option to deprecate the old method names and then a 1.1 release. (or 1.0.1 if you like that more) That way people can gradually migrate to the new version.
Avoid naming conflicts with Hamcrest's hasValue Resolves issue #24, but chose different names to allow for fluent method chains like: