Rules shouldn't rely on `this`

[SimenB]

They should receive what they need as arguments, and return/invoke a callback with a result.

• [ ] They shouldn't call this.msg() internally.
• [ ] They shouldn't use this internally, get all data passed as arguments.
• [ ] Return result object: { line: 0, column: 0, message: "Colon missing." }
  • We know severity and name of rule at call time
  • Be inspired by http://eslint.org/docs/developer-guide/working-with-rules#contextreport
• [ ] Update all tests.

[SimenB]

@wojciechczerniak Getting back to this, finally.

What do you think about calling each rule with the full source instead of a single line at a time? It means every rule have to handle disable-comments (or we can strip them out before hand), but it makes it easier to reason about the state of the rule itself.

Still not sure what the best API is here.

[SimenB]

I'd like to release an alpha of v2 after this is done.