coc-metals
Advanced tools
coc-metals - npm Package Compare versions
Comparing version 0.7.1 to 0.7.2
| { | ||
| "name": "coc-metals", | ||
| "version": "0.7.1", | ||
| "version": "0.7.2", | ||
| "description": "coc.nvim extension for Metals, the Scala language server", | ||
@@ -292,3 +292,3 @@ "keywords": [ | ||
| "devDependencies": { | ||
| "@types/node": "^13.7.7", | ||
| "@types/node": "^13.9.1", | ||
| "npm-run-all": "^4.1.5", | ||
@@ -302,6 +302,6 @@ "parcel-bundler": "^1.12.4", | ||
| "dependencies": { | ||
| "coc.nvim": "0.0.75", | ||
| "coc.nvim": "0.0.76", | ||
| "metals-languageclient": "0.1.20", | ||
| "promisify-child-process": "^3.1.3", | ||
| "vscode-languageserver-protocol": "3.15.0-next.6" | ||
| "vscode-languageserver-protocol": "3.15.3" | ||
| }, | ||
@@ -308,0 +308,0 @@ "resolutions": { |
@@ -192,7 +192,13 @@ | ||
| Metals allows users to create a `*.worksheet.sc` file and see evaluations right in the file. In Vim, | ||
| this is done using comments that are inserted which will allow you to hover on them to expand. In | ||
| Neovim, this is done using Neovim's [virtual text](https://neovim.io/doc/user/api.html#nvim_buf_set_virtual_text()) | ||
| to implement Metal's [Decoration Protocol](https://scalameta.org/metals/docs/editors/decoration-protocol.html). | ||
| If using Neovim, make sure to have the following line in included in your `.vimrc` along with your `coc.nvim` mappings. | ||
| Metals allows users to create a `*.worksheet.sc` file and see evaluations right | ||
| in their file. In Vim, this is done using comments that are inserted which will | ||
| allow you to hover on them to expand. In Neovim, this is done using Neovim's | ||
| [virtual text](https://neovim.io/doc/user/api.html#nvim_buf_set_virtual_text()) | ||
| to implement Metal's [Decoration | ||
| Protocol](https://scalameta.org/metals/docs/editors/decoration-protocol.html). | ||
| If using Neovim, make sure to have the following line included in your `.vimrc` | ||
| along with your `coc.nvim` mappings. Also keep in mind that the worksheet needs | ||
| to be created inside of your project to have access to your dependencies etc. If | ||
| you create them in the root of your project for example, your worksheet will | ||
| only have access to the standard lib. | ||
@@ -235,3 +241,3 @@ ```vim | ||
| - `metals.build-connect` | ||
| - `metails.build-restart` | ||
| - `metals.build-restart` | ||
| - `metals.sources-scan` | ||
@@ -316,4 +322,4 @@ - `metals.compile-cascade` | ||
| It's recommended to use a statusline integration with `coc-metals` in order to | ||
| allow messages to be displayed in your status line rather than as a message. This | ||
| will allow for a better experience with as you can continue to get status | ||
| allow messages to be displayed in your status line rather than as a message. | ||
| This will allow for a better experience as you can continue to get status | ||
| information while entering a command or responding to a prompt. However, we | ||
@@ -329,11 +335,13 @@ realize that not everyone by default will have this setup, and since the user | ||
| Again, it's recommended to make this active, and use a statusline plugin, or | ||
| manually add the coc status information into your statusline. | ||
| `coc.nvim` has multiple ways to integrate with various statusline plugins. You can find instructions | ||
| for each of them located [here](https://github.com/neoclide/coc.nvim/wiki/Statusline-integration). | ||
| If you're unsure of what to use, [vim-airline](https://github.com/vim-airline/vim-airline) is a | ||
| great minimal choice that will work out of the box. | ||
| manually add the coc status information into your statusline. `coc.nvim` has | ||
| multiple ways to integrate with various statusline plugins. You can find | ||
| instructions for each of them located | ||
| [here](https://github.com/neoclide/coc.nvim/wiki/Statusline-integration). If | ||
| you're unsure of what to use, | ||
| [vim-airline](https://github.com/vim-airline/vim-airline) is a great minimal | ||
| choice that will work out of the box. | ||
| With [vim-airline](https://github.com/vim-airline/vim-airline), you'll notice two noteworthy, | ||
| things. The first will be that you'll have diagnostic information on the far | ||
| right of your screen. | ||
| With [vim-airline](https://github.com/vim-airline/vim-airline), you'll notice | ||
| two noteworthy things. The first will be that you'll have diagnostic | ||
| information on the far right of your screen. | ||
@@ -350,4 +358,5 @@  | ||
| If you don't use a statusline plugin, but would still like to see this information, the easiest | ||
| way is to make sure you have the following in your `.vimrc`. | ||
| If you don't use a statusline plugin, but would still like to see this | ||
| information, the easiest way is to make sure you have the following in your | ||
| `.vimrc`. | ||
@@ -354,0 +363,0 @@ ```vim |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by0.12%
195124
- Number of lines in readme file
- increased by2.28%
403
Dependency changes
+ Addedcoc.nvim@0.0.76(transitive)
+ Addedvscode-jsonrpc@5.0.1(transitive)
+ Addedvscode-languageserver-protocol@3.15.3(transitive)
+ Addedvscode-languageserver-types@3.15.13.17.5(transitive)
- Removedcoc.nvim@0.0.75(transitive)
- Removedvscode-languageserver-types@3.15.0-next.2(transitive)
Updatedcoc.nvim@0.0.76