You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a relatively new linter for Clojure, clj-kondo which has lately gained a lot of popularity among Clojure devs for being a very well thought out and comprehensive Clojure linting tool. It is also designed to be integrated quite easily, as is proven by its Editor Integration (clj-kondo) page.
However, things could be even better. While by default clj-kondo outputs mainly text describing linting problems, it also has a raw data analysis output mode which could be used as an excellent basis for eg. driving refactorings, live templates and whatever features provided natively by the IntelliJ platform. Of course just highlighting the correct parts of the file is a start, and quite close to what File Watchers already does, but using actual analysis data would open up a lot of paths for deeper IDE integration further along the way.
The text was updated successfully, but these errors were encountered:
There's a relatively new linter for Clojure, clj-kondo which has lately gained a lot of popularity among Clojure devs for being a very well thought out and comprehensive Clojure linting tool. It is also designed to be integrated quite easily, as is proven by its Editor Integration (clj-kondo) page.
However, things could be even better. While by default clj-kondo outputs mainly text describing linting problems, it also has a raw data analysis output mode which could be used as an excellent basis for eg. driving refactorings, live templates and whatever features provided natively by the IntelliJ platform. Of course just highlighting the correct parts of the file is a start, and quite close to what File Watchers already does, but using actual analysis data would open up a lot of paths for deeper IDE integration further along the way.
The text was updated successfully, but these errors were encountered: