.satisfies()
is too verbose, .notSatisfies()
and .notDeepEquals()
are of little use
#47
Labels
enhancement
New feature or request
In
o(myObject).satisfies(myValidator(someSepcification))
, thesatisfies
bit takes too much space and hampers readability.o(myObject)._(matches(someSepcification))
would make more readable tests.Also, the
.notSatisfies()
and.notDeepEquals()
assertions are not very useful, and even IMO an anti-pattern, as any difference will make them pass, not necessarily the one the tester had in mind when designing the test. They should be. retired.Here's the roadmap I propose
For v4.2.0:
Add
._()
as a synonym to.satisfies()
.Make
o.warn = false
. If the user setso.warn = true
, have.satisfies
,.notSatisfies
and.notDeepEquals
issue warnings announcing future obsolescence (we can do that cleanly such that a single list is reported after publishing the report).For v5.0.0
Make the warning unconditional, and state that the methods are deprecated.
Sometimes in the future
Remove them altogether.
The text was updated successfully, but these errors were encountered: