nvim-lspconfig/lua/lspconfig/server_configurations/purescriptls.lua, branch docs[no description]http://git.sudomsg.com/mirror/nvim-lspconfig/atom?h=docs2024-10-01T12:39:12Zrefactor: rename "server_configurations" => "configs" #33302024-10-01T12:39:12ZJustin M. Keyesjustinkz@gmail.com2024-10-01T12:39:12Zurn:sha1:bedb2a0df105f68a624a49b867f269b6d55a2c89
Problem:
The name `server_configurations` is extremely verbose and irritatingly
formal and dogmatic. This overlong name is a constant nuisance when
reading, writing, and coding.
It's also not even correct: these configurations are just as much
"client" configurations as they are "server" configurations.
Solution:
- Rename to a shorter name.
- Leave placeholder files for any old URLs that link to the old
location.fix(purescript-language-server): add 'spago.yaml' to the list of root_patterns (#3022)2024-02-23T05:34:16Zklausweissmbiel@mailbox.org2024-02-23T05:34:16Zurn:sha1:58310212b8aad3d53e7182437f4425491fe16418fix: use exepath on server command (#2595)2023-05-09T07:10:14ZRaphaelglepnir@neovim.pro2023-05-09T07:10:14Zurn:sha1:4a69ad6646eaad752901413c9a0dced73dfb562dfix(purescript-language-server): root dir for Nix files #19542022-06-12T17:37:16Ztoastal561087+toastal@users.noreply.github.com2022-06-12T17:37:16Zurn:sha1:7a9c0485456b58ad0eb1e138030f12a4d4d29e96
As seen in the source code:
https://github.com/nwolverson/purescript-language-server/blob/db5584d79e698b02e3df12a1299d5f93262bd5ee/src/LanguageServer/IdePurescript/Main.purs#L391
Nix-related files were added to the Language server to establish the
root. This commit looks to mimic that behavior. The PureScript community
has a lot of Nix-positive users and tooling.
Additionally the docs were updated::
* Reflect the new `root_dir` + `root_pattern` list
* Include a list of ways to install the language server to your project
* Remove the specific, problematic npm install command because
** Globally installing these tools is a bad practice as teams should
maintain consistent versions in their projects and users are less
likely to remember to upgrade global packages; new documentation
suggests to add it to your project, but it doesn’t _not_ say to
install it globally if desired
** npm is _not_ the only JavaScript package manager
** JavaScript package managers are not the only way to get the language
server
** Unrelated but technically incorrect: the block was labeled as a shell
script despite it being a shell session (code block syntax `sh`
should be `console`)chore: remove all package.json (#1656)2022-02-25T17:02:19ZMichael Lingelbachm.j.lbach@gmail.com2022-02-25T17:02:19Zurn:sha1:700eda91316a876757bf306fd709fde75aadb36afix(npm): resolve the command correctly on windows2021-12-08T08:09:25Zkylo25259826753+kylo252@users.noreply.github.com2021-12-01T08:03:10Zurn:sha1:a2719a8723e503f1be89d9b1c334846de405eb23chore: clean up imports2021-11-26T04:46:21ZMichael Lingelbachm.j.lbach@gmail.com2021-11-25T17:40:39Zurn:sha1:97da7ed12e7e0d86e735e38a8170e941d4ed3e9afeat: expose configs2021-11-26T04:46:21ZMichael Lingelbachm.j.lbach@gmail.com2021-11-25T04:01:07Zurn:sha1:6c2fb86c6a03e20abea5ddd17d735885f0b7cb5e