Fixes/explanations are missing from all warnings

[MostAwesomeDude]

While django-lint finds many things it does not like about my applications, it is not very forthcoming with why things are bad, and how I can fix them.

[sethwoodworth]

I agree, the messages are a little terse. Static checkers warning and errors tend to be short so they can be integrated into IDEs and shell scripts. Would docs mapping an error message to how to handle the problem, or why something is considered poor code smell do? I think I'd like to write that.

[MostAwesomeDude]

Definitely, docs would be so nice.

I sat down with #django and pulled some teeth to get explanations on
many of the model-related warnings. It'd be helpful to explain why
things are bad, but even better to explain how things could be fixed
by the programmer performing maintenance.

On Sat, Jul 7, 2012 at 1:24 AM, Seth Woodworth
[email protected]
wrote:

I agree, the messages are a little terse. Static checkers warning and errors tend to be short so they can be integrated into IDEs and shell scripts. Would docs mapping an error message to how to handle the problem, or why something is considered poor code smell do?

---

Reply to this email directly or view it on GitHub:
#11 (comment)

When the facts change, I change my mind. What do you do, sir? ~ Keynes

Corbin Simpson
[email protected]

[sethwoodworth]

PyLint documentation exists as a wiki. Could be more complete, but the lack of docs is a PyLint issue, not a django-lint issue it seems.