> On Jun 22, 2017, at 10:14 AM, Justin Mclean <jus...@classsoftware.com> wrote: > > Hi, > >> The main argument for using strict equality is because it does type >> conversions which can cause bugs. > > Incorrect strict equality doesn’t do type conversion, but I assume you meant > to say "it doesn’t do type conversion”.
By “it” I meant regular equality. >> Since we are using a strongly typed language, type safety is generally >> enforced by the compiler > > Expect were we’re comparing with undefined which we are currently doing for > just about every Object, String and Number in the SDK on the JS side. Exactly. And all those should NOT use strict equality.
