Laurent VERDOÏA

Public release and tagging

1

When you go on the repository page, you can see that there is only one release : v1.0.0 on 23 June 2017 This can make think a lot of people...

Spec conformance for errors

1

Do not emit JSON when there is no error locations Just conform to the spec : 7.1.2 If an error can be associated to a particular point in the requested...

Since there is no link to documentation published on [GitHub Pages](https://pages.github.com/), online documentation is hard to find. In this pull request, i add the link inside the file `README.md` to...

go.mod: Upgrade go min version to 1.18

4

This will permit to use generics in future merge requests

Since has shown in #7, we need to drain the buffer to do not block the A operation when full. We should permit user to select another implementation to overcome...

Since capture is implemented with a pipe, write are blocked when the buffer is full. But this is not explicitly written inside the documentation.

It can be useful to record distinctly stdout and stderr. Maybe, during unit-testing, you can separately check stdout and stderr output.

Add a CLI argument to specify the configuration file

2

When you use a linter collection tool like [MegaLinter](https://megalinter.io/), by default, we put all the configuration files into the folder `.github/linters`. And thus, if you create `.github/linters/.v8rrc.yml`, this cannot be...

Default golangci-lint configuration produces schema validation errors

2

### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior The file `TEMPLATES/.golangci.yml` still contains configuration about deprecated and deleted linters...