Sometimes it happens that we're stuck in ClassPath hell. Which means that there's two conflicting dependencies, both putting the same class (but different!) on the classpath, and it's random which one will be first.
There's a way to find out.
So I wanted to use the new "strict" settings when compiling my Angular apps.
This is a small blog on the issues I ran into.
Luckily, similar issues can be found when you move over to Kotlin from Java.
I've posted links in the References below of blog posts that delve deeper into the strict setting.
Check everything, because suddenly we have values everywhere (perhaps due to point 1 above) and checks for existing values now always turn true.
Where a null value was previously sent appropriately to the rest service, suddenly it has an initial value of '', and now the parsing of the JSON fails.
