The most annoying thing for me (other than seemingly arbitrary changes
causing whole suites to fail despite correct functionality) is that it
breaks duck typing and causes code like:
if (obj.quacks) {
...
}
to fail tests. So in these cases, we are forced to write code something
like:
if (obj.quacks || false) {
...
}
to sidestep warnings. It doesn't make the code any more readable or
safe, its just an arbitrary change to please an arbitrary linter.
There is real pain we are feeling while dealing with these
strict-warnings-as-errors, and only hand wavy benefit. As Eddy said,
strict warning free code is not a goal for devtools, it is just
something we are forced to do instead of work on whatever we are
actually trying to do!
Nick
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
