Earlier quoted context omitted.
It might be interesting to split those native linters out into separate projects so that other meta-linters like flycheck, check-all-the-things, various IDEs etc can also use them.
Indeed. However, you can run just those native linters with coala too (on specific files or entire projects). And we currently have plugin support for a few editors.
PMD source code analyzer
31–36 of 36 posts
Re: PMD source code analyzer
#32Earlier quoted context omitted.
Indeed. However, you can run just those native linters with coala too (on specific files or entire projects). And we currently have plugin support for a few editors.
What is the command for only running the native linters?
You could take a look at the list of bears we support[1] (a bear is basically a plugin) though.
Re: PMD source code analyzer
#33Earlier quoted context omitted.
What is the command for only running the native linters?
There isn't really a command for just native linters - there is practically no difference between a native one and an external one. You could take a look at the list of bears we support[1] (a bear is basically a plugin) though. [1] https://github.com/coala/bear-docs
Re: PMD source code analyzer
#34Earlier quoted context omitted.
There isn't really a command for just native linters - there is practically no difference between a native one and an external one. You could take a look at the list of bears we support[1] (a bear is basically a plugin) though. [1] https://github.com/coala/bear-docs
Is there a way to disable the non-native linters?
You can use just that bear:
[Commit]
bears = GitCommitBear
shortlog_trailing_period = False # disallow periods at the end of the shortlog
You can have other sections too (imagine the following section is in the same file as the above): [LineLength]
bears = LineLengthBear
files = *.py
max_line_length = 80
Again, LineLengthBear is a native solution.Of course, you can also combine native and external linters in the same section - they are virtually the same to the user.
Re: PMD source code analyzer
#35I've checked out Coala, I've been using FindBugs and SonarQube in the past, and sadly, all of the solutions I've seen miss support for Lisp language family. I could use some kind of linter for my Common Lisp code.
Hey, would it help you if we were to include https://github.com/fukamachi/sblint in coala? Do you know other tools? We could easily integrate them using https://api.coala.io/en/latest/Developers/Writing_Linter_Bea... if there's concrete interest
I haven't used the one you linked to yet (thanks for the link!). Seems like it could be useful.
Re: PMD source code analyzer
#36Earlier quoted context omitted.
Is there a way to disable the non-native linters?
You can specify exactly which linters you want though a coafile (a config file). For example, we have something called a GitCommitBear that lints your git commit messages. It's entirely written by us. You can use just that bear: [Commit] bears = GitCommitBear shortlog_trailing_period = False # disallow periods at the end of the shortlog You can have other sections too (imagine the following section is in the same fil…