
In unit tests, assertions inside if-clauses risk being silently skipped. We discuss some tips and best practices to avoid situations where assertions live in if-clauses.

There's one key qualifier in this sentence: I know. One's skill set matters, I guess...
The post talks about how to avoid ifs ;)
In unit tests, assertions inside if-clauses risk being silently skipped. We discuss some tips and best practices to avoid situations where assertions live in if-clauses.
Generally, it is inadvisable to directly expect in if-clauses. Here are some tips to avoid these situations.
Yes, I agree. Too many people are overly obsessed with the exact definition of "Open Source". But come on, this now "proprietary" software is only tiny bit different from an open source software and shares almost no similarity with a typical proprietary software.
And more importantly, this new license is even arguably better than an open core model.
Using a third-party library when it's applicable definitely works. Much of this post is for those who can't add a heavy dependency :)
A Type-Safer Alternative to Type Guards in TypeScript
A trick that I'd like sharing :)
Oops, seems like already dead :\
I would just use the part that I consider good.