diff --git a/docs/_manual/00-why-what-how.md b/docs/_manual/00-why-what-how.md index 27f181c7d..e4d7e3f06 100644 --- a/docs/_manual/00-why-what-how.md +++ b/docs/_manual/00-why-what-how.md @@ -21,10 +21,7 @@ You get 100% coverage and the confidence that all the requirements of the `equal There is one downside to this. EqualsVerifier is an opinionated tool. It has to be. Unfortunately, that means it can feel restrictive to some people: -

All right. Goodbye. EqualsVerifier. I cannot handle your needless constraints.

— ☕ J. B. Rainsberger (@jbrains) November 3, 2015
- - -
+[![Tweet by JB Rainsberger saying: "All right. Goodbye. EqualsVerifier. I cannot handle your needless constraints."]({{ site.baseurl }}/images/needless-constraints.png)](https://twitter.com/jbrains/status/661556171166392320) This manual is an attempt to explain these constraints are necessary. It also explains how you can remove the constraints if you don't agree with them. If you still feel EqualsVerifier is too restrictive, then that's fine; you don't have to use it if you don't want. But if you do, the quality of your `equals` methods will improve, and so will your test coverage. diff --git a/docs/images/needless-constraints.png b/docs/images/needless-constraints.png new file mode 100644 index 000000000..84c878b3b Binary files /dev/null and b/docs/images/needless-constraints.png differ