Update react/sort-comp eslint rule

We were using the default ordering for sort-comp. The new ordering is:

"type-annotations",
"static-methods",
"lifecycle",
"everything-else",
"render"

Upgrade to ESLint v3

This upgrades the ESLint linter to v3. Everything should work the same with two notable rule exceptions:

• Disabled react/sort-prop-types (after discussion in the Web Frontend meeting that this wasn't useful)
• Disabled no-case-declarations (this was causing problems with a common code pattern used in Redux-style code)

jshint ☛ eslint

From @csilvers email:

It took a bit longer than expected, but the new javascript linter, eslint, is now live in prod! You may start seeing lint errors you've never seen before.

Let me know if you find any of the new lint rules onerous or just ugly. We want to end up with lint rules that really help our codebase with minimal cost to developers.

To help with that, I've added some autofixing mojo into arc lint, to fix up some common lint errors. If your commit is suddenly running into lint problems when you run git commit, try running arc lint to see if it will help you out. If there are errors you're seeing a lot that there's no autofix for, let me know and I'll see how practical it is to add one.

Happy linting!

Two new linters (Python Extras, Less.js), Linting merge commits

• 9f5f41b Add lesshint to khan-linter
• 220723d Rename util.py to lint_util.py.
• 78ebd40 Add a new linter, which extends the work of pyflakes/pep8.
• 58d477e Take 2 at properly linting merge commits.

bugfix: don't fail if docstring on the first line of a file is too long

• Contains bugfix 323c7a6 by @csilvers

first packaged release

first semantically versioned release, started at v1.1 since there is a bit of a history in this repo already.