New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation explaining the different mistakes/style issues detected #936
Comments
Thanks! I think that would certainly be good to add. I've also been meaning to add a full list of all possible linters for the configuration page (https://github.com/borkdude/clj-kondo/blob/macros-sci/doc/config.md). As for https://blog.michielborkent.nl/2017/05/25/inline-def-debugging/ |
Adding a list of the linters would really help newcomers as well! And yeah, after some Googling, and some docs reading, I found out why the Anyway, thanks for |
@Tiv0w The list is now available here: https://github.com/borkdude/clj-kondo/blob/master/doc/linters.md. |
Looks great to me! It will help me upgrade a project which was using an old clj-kondo dep. (I assume the list is exhaustive) |
@vemv Yes, the list is (or should be) exhaustive. |
Problem
Hello, I'm a super beginner with Clojure, and using
clj-kondo
I'm sometimes not helped at all. I make mistakes in my code (which is normal as a beginner),clj-kondo
tells me about these errors, but I absolutely don't know what to do with an information like:I'm willing to refactor it to something better, but I don't know what to refactor it to!
I also don't know if it's a logic issue or a style issue.
Solution
At least a simple Markdown or text file to list and document the potential errors/warnings thrown by
clj-kondo
, and indications on how to refactor them (in my above example: change inline def to alet
binding).Alternatives
Rust tooling provides with the linter a
--explain [ERROR CODE]
command, which prints a small explanation of the error, and most of the times how to remedy to the given error.I could try to collect and gather information and documentation about the errors as I learn and then open a PR, but I think we're all better off with the documentation of someone who actually knows Clojure and why those errors are being reported. (Not me 😇 )
The text was updated successfully, but these errors were encountered: