| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
It's supposed to be a path to the TypeScript server folder, not a file.
|
| |
|
|
|
|
|
|
|
|
| |
`@astrojs/language-server@2.0.0` utilizes Volar language server under
the hood. The LSP's init_options are located [here][1].
`typescript.serverPath` has been renamed to `typescript.tsdk`. There is
no `configuration`; that option is for the VSCode extension, located in
the `astro-vscode` package [here][2].
[1]: https://github.com/volarjs/volar.js/blob/dfc8ccefb6c3aa53bd0eb9755259538a11127edd/packages/language-server/src/types.ts#L50
[2]: https://github.com/withastro/language-tools/blob/eb2ce0b3effd00e49294be57ef0f3d1cb5f8f454/packages/vscode/package.json#L126
|
| | |
|
| |
|
|
| |
As of version 0.24 of the LSP, a `typescript` field is required, with
the same convention as `volar`.
|
| |
|
