Closed rami3l closed 1 week ago
Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:
Proper conventional commit scoping:
If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin
If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error
[x] Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above
[x] README
is properly formatted and uses fenced in links with <url>
unless they are inside a [title](url)
[x] Proper usage of opts
table rather than setting things up with the config
function.
The fact that this is needed due to the hard error is just stupid...Thanks!
📑 Description
This prevents the error message that comes with the newer versions of
go.nvim
:https://github.com/ray-x/go.nvim/blob/b3ee7aea17d5b7acd1e3007efa7ac0e43947ad0c/lua/go.lua#L233-L235
ℹ Additional Information
I think the author could've given a good default to this value and make it overridable instead of issuing a hard error, but alas...
Tested with the following config override locally: