5 ms·

Another meta-linter: https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git https://anonscm.debian.org/cgit/collab-maint/check-all-the-t...

adtac 10y ago
Actually, coala is not entirely a meta-linter - we have a few native linters that we wrote ourselves too. However, a large chunk is external linters.
- BuuQu9hu 10y ago
  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.
  - adtac 10y ago
    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.
    - BuuQu9hu 10y ago
      Do your linters support the Firehose static analysis results format?
      - adtac 10y ago
        I'm not entirely sure what that format is, but coala can be formatted to output in any format you want using a `--format` flag. You have the result components such as message, line number, line, and several other parameters and you can build your own line. And if that's not enough, you can also output as JSON. Edit: and this applies to all linters - native and external.
        BuuQu9hu 10y ago
        https://github.com/fedora-static-analysis/firehose https://github.com/fedora-static-analysis/firehose
        adtac 10y ago
        Interesting. I just took a look at the examples. We don't have support for SHA-1 sums for example, but these could be added very easily. I've created an issue to support this in coala: https://github.com/coala/coala/issues/3525 https://github.com/coala/coala/issues/3525 Thanks!
    - BuuQu9hu 10y ago
      What is the command for only running the native linters?
      - adtac 10y ago
        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 https://github.com/coala/bear-docs
        BuuQu9hu 10y ago
        Is there a way to disable the non-native linters?
        adtac 10y ago
        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 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.
        BuuQu9hu 10y ago
        Hmm, was thinking something command-line would be easier.

adtac 10y ago

Actually, coala is not entirely a meta-linter - we have a few native linters that we wrote ourselves too. However, a large chunk is external linters.

BuuQu9hu 10y ago
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.
- adtac 10y ago
  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.
  - BuuQu9hu 10y ago
    Do your linters support the Firehose static analysis results format?
    - adtac 10y ago
      I'm not entirely sure what that format is, but coala can be formatted to output in any format you want using a `--format` flag. You have the result components such as message, line number, line, and several other parameters and you can build your own line. And if that's not enough, you can also output as JSON. Edit: and this applies to all linters - native and external.
      - BuuQu9hu 10y ago
        https://github.com/fedora-static-analysis/firehose https://github.com/fedora-static-analysis/firehose
        adtac 10y ago
        Interesting. I just took a look at the examples. We don't have support for SHA-1 sums for example, but these could be added very easily. I've created an issue to support this in coala: https://github.com/coala/coala/issues/3525 https://github.com/coala/coala/issues/3525 Thanks!
  - BuuQu9hu 10y ago
    What is the command for only running the native linters?
    - adtac 10y ago
      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 https://github.com/coala/bear-docs
      - BuuQu9hu 10y ago
        Is there a way to disable the non-native linters?
        adtac 10y ago
        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 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.
        BuuQu9hu 10y ago
        Hmm, was thinking something command-line would be easier.