Jedi-language-server

Latest version: v0.42.0

Safety actively analyzes 681866 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 11 of 18

0.23.1

Fixed

- workspace/didChangeConfiguration option is now defined. It currently does nothing, but this resolves some feedback errors on some language clients. See <https://github.com/pappasam/jedi-language-server/issues/58>.

0.23.0

Added

- Implemented `completionItem/resolve`; the Jedi completion data are held until the next `textDocument/completion` arrives
- Added `completion.resolveEagerly` option to allow users to opt out of the change (in anticipation for their editor to support `completionItem/resolve` if it does not already)

0.22.0

Changed

- Support only jedi `0.18.0`. Stopped using `from_fs_path` from pygls, using `as_uri` method on the returned pathlib.Path objects instead. Note: older versions of Jedi are not supported by this version.

0.21.0

Added

- The ability to add extra paths for your workspace's code completion (`"workspace.extraPaths"`). Thanks to [Karl](https://github.com/theangryangel) and his [PR](https://github.com/pappasam/jedi-language-server/pull/39) which inspired this feature.

Changed

- Only 1 Jedi project is created / managed by jls. In the past, a new project was created on a per-call basis. This may have positive performance implications.

0.20.1

Fixed

- documentSymbol now classifies methods/properties somewhat correctly
- Replace unnecessary private attribute access within jedi with self-managed constant

0.20.0

Changed

- Update documentSymbol query
- Uses native Jedi position finders (faster)
- Removes noisy symbols from hierarchical output. Makes document outliners prettier / more visually useful

Page 11 of 18

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.