On Fri, Dec 19, 2014 at 2:22 PM, Nick Fitzgerald <nfitzger...@mozilla.com> wrote:
> I generally don't find them useful, but instead annoying, and that they > provide a lot of noise to filter out to find actual relevant errors. This > is including the undefined property errors. It is a common JS style to pass > around configuration/option objects that will be missing many properties > that get accessed by functions they are passed to. My understanding is that > part of this is special cased not to generate these messages, but in my > experience it isn't close to enough. > In a recent message, Jason explained that code that tests for the presence of a property: if (obj.prop) if (obj.prop === undefined) if (obj.prop && ...) are not supposed to generate warnings. Do you find that you're getting these warnings from code that has one of those forms? _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
