Jeroen de Jong

As noted in #93, this issue is best to be picked up after the reporter is available for the whole stack. This issue could be implemented initially for just the...

I guess comparing the quoted spec is fine, the main issue is that the param isn't unquoted. e.g. ```clj user> (= '(clojure.spec.alpha/nilable #{1}) '(clojure.spec.alpha/nilable #{1})) true ``` but right now...

> If the CI integration was analog to https://github.com/DeLaGuardo/clojure-lint-action , namely applying a diff over a PR's changes only, maybe #132 wouldn't be that necessary. This issue overarches the CI...

I think the priority is lower since the biggest linters ship with good ignore syntax nowadays. However I think a way to ignore built in linters is required before this...

an alternative would be to suppress any printing and expecting a report for any action (formatting/linting) which can be handled more fine grained. These reports could be manipulated to provide...

> I think some just println, w/o offering a data-oriented API That's true, but because we internally call the linters with 1 file only (usually), we could construct a bare...

Thanks for the issue, this seems like a good suggestion! It's a good idea to make a definitive list of the supported / unsupported macros (especially interested in the latter)....

Woah this is a pretty cool plugin!

carve also has a dry-run option + can format 👍 Looking good

Using a boolean now prevents expansion in the future. What do you think about returning a map? It can yield `:result?` now, and possibly reports or tested-files in a later...