On 12/26/2014 5:59 PM, Jeff Walden wrote: > On 12/22/2014 08:08 AM, Paolo Amadini wrote: >> Maybe we could make available >> an opt-in code linting solution - and these typos would become errors, >> not warnings, > > Introducing our own proprietary version of JS with these as errors
To clarify, these would be linting errors, just like it would be an error to inconsistently indent a line by one space instead of two. An automated tool in Continuous Integration could then tell you in advance that your patch will be rejected if this is not fixed (so the reviewer doesn't have to do the check or detect typos manually). > creates a purely self-inflicted language But I agree we may not want to enforce this particular check during code linting, and allow a more liberal style, even for chrome code (that by our choice has higher requirements than web page code). If you're thinking about the usefulness of these warnings for web page authors, my guess is that it would be quite limited, for the reasons you mentioned. Paolo _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
