nvim-lspconfig/lsp/golangci_lint_ls.lua, branch docs

fix(golangci_lint_ls): disable all output formats except JSON #4247

2026-01-27T13:25:39Z

This change set enables all possible output formats that exist for golangci-lint. This is necessary because if a user configures output formats in their `.golangci.yml` configuration (for example for CI) then this is always in addition to the ones enabled on the command line. Therefore, we manually disable all possible output formats. Currently, there doesn't exist a `golangci-lint` option to exclusively enable an output format or disable all from the config.

fix: separate type annotation from `@brief` docstring #4017

2025-08-20T02:13:01Z

chore: add type annotation for configs

2025-08-19T02:39:23Z

fix(golangci_lint_ls): support v2 wrapper script #3984

2025-08-06T02:03:23Z

feat(golangci_lint_ls): add support for v1 #3865

2025-05-22T10:52:59Z

docs: cleanup

2025-04-18T15:44:38Z

- brief should live at the top of each file - fix indentation for some docs

feat: migrate to vim.lsp.config #3659

2025-04-12T22:15:43Z

Problem: Nvim 0.11 has vim.lsp.config, which mostly replaces the legacy nvim-lspconfig "framework". Solution: Migrate all configs to `lsp/*` variants. The old configs in `lua/lspconfig/` are "frozen". The new configs include these changes: - `commands` field became raw calls to `vim.api.nvim_buf_create_user_command` inside `on_attach`. - `root_dir` became: - `root_markers` whenever the file list was simple didn't need to mach `*` - if the logic was complicated, or needed to match something like '\*.c', it was defined as a vim.lsp.Config `root_dir` callback. - `on_config_change` became `before_init`. I don't actually know if this is the correct approach, but looking around the documentation of `nvim-lspconfig` a saw that it was defined as the function that gets called as soon as the config have `root_dir`, and so I thought `before_init` might be the closest alternative. - `docs.description` became a luadoc `@brief` docstring. - `single_file_support = false`? Co-authored-by: Aliou Diallo Co-authored-by: Justin M. Keyes