aboutsummaryrefslogtreecommitdiffstats
path: root/.github/ISSUE_TEMPLATE/package_issue.yaml
Commit message (Collapse)AuthorAgeFilesLines
* docs: update references to mason-org/mason.nvim (#1925)William Boman2025-05-061-1/+1
|
* chore!: update required Neovim version to 0.10.0William Boman2025-02-191-2/+2
|
* feat!: upgrade minimum required neovim version to 0.9.0 (#1517)William Boman2025-02-161-2/+2
|
* chore: update issue template (#1274)William Boman2023-04-281-4/+2
|
* chore: update issue templates (#1273)William Boman2023-04-281-4/+2
|
* chore: update issue templates (#572)William Boman2022-10-181-47/+38
|
* chore: update issue templates (#230)William Boman2022-08-021-8/+22
|
* chore: clean up package issue template (#153)William Boman2022-07-251-16/+0
|
* refactor!: extract mason-lspconfig to separate plugin (#109)William Boman2022-07-221-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | The rationale behind this is to make boundaries clearer as mason.nvim has no direct relation with lspconfig per se. Also, hopefully, by having it as a separate package like this would encourage more people to write similar extensions (think mason-dap and mason-null-ls). Ideally such extensions wouldn't be required at all, but there are definitely gaps to fill as of today. From now on you'll need to add `williamboman/mason-lspconfig.nvim` as a plugin if you want to use the `mason-lspconfig` extension: ```lua use { { "williamboman/mason.nvim", branch = "alpha" }, "williamboman/mason-lspconfig.nvim", "neovim/nvim-lspconfig", } ``` ```lua Plug "williamboman/mason.nvim", { 'branch': 'alpha' } Plug "williamboman/mason-lspconfig.nvim" Plug "neovim/nvim-lspconfig" ```
* chore: fix some wording (#24)William Boman2022-07-081-1/+1
|
* chore: adjust some remnants of nvim-lsp-installerWilliam Boman2022-07-071-0/+117