| 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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* feat: add basedpyright support
* fix(basedpyright): correct settings schema
Settings are stored under a different key for this fork. Instead of
using the original `python` key, now settings specific to this LSP
server are stored under `basedpyright` map key.
* fix(basedpyright): correct plugin command
The command was doing nothing because as `python` is no longer the
default namespace for settings, for this LSP server,
`client.settings.python` has a `nil` value. Hence the table couldn't be
extended.
|
| |
|
|
|
|
|
|
|
| |
* feat: add basedpyright support
* fix(basedpyright): correct settings schema
Settings are stored under a different key for this fork. Instead of
using the original `python` key, now settings specific to this LSP
server are stored under `basedpyright` map key.
|
| |
|
