Seth Daniel

likely a json file in the project root. perhaps support one or more of the many projects that already do this.

https://github.com/jose-elias-alvarez/null-ls.nvim/wiki/Avoiding-LSP-formatting-conflicts

Since `go.work` can support multiple modules it's possible that `go list -m` will return more than one result.

perhaps `vim.notify` should be used when logging.

Is it the first part of a bigger subsystem w/i Goldsmith or a useless appendage?

Figure out why and fix, if needed.

Warn the user if a treesitter parser that is needed for go code, is not available. Currently this means the `go`, `gomod`, and `gowork` parsers.

Fuzzy testing is a new feature of 1.18. The testing commands should support it.

``` $ vim --version NVIM v0.7.0-dev Build type: RelWithDebInfo LuaJIT 2.1.0-beta3 Compilation: /usr/bin/cc -g -O2 -ffile-prefix-map=/build/neovim-TaFwuh/neovim-0.7.0~ubuntu1+git202203110047-6170574d2-dd05b3569=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -DNVIM_TS_HAS_SET_ALLOCATOR -O2 -g -Og -g -Wall...