Skip to content

Latest commit

 

History

History
89 lines (56 loc) · 3.78 KB

CHANGELOG.md

File metadata and controls

89 lines (56 loc) · 3.78 KB
Raw

Changelog

All notable changes between releases will be documented in this file.

The format is based on Keep a Changelog.

Unreleased

Nothing here, yet.

v0.2.4 - 2022-01-31

Changed

  • Disabled another problematic test on x86_64-darwin, see #76 for context (from @Ma27).

v0.2.3 - 2021-12-24

Changed

  • Fixed nixpkgs-fmt crate to keep rnix-lsp publishable (from @Ma27).

v0.2.2 - 2021-12-24

Added

  • Updated rnix to v0.10.1 for support of new Nix 2.4 language features (from @Ma27).
  • Disabled a test that's flaky on Darwin to fix the darwin build (from @peterbecich).

v0.2.1 - 2021-09-23

Changed

  • Fixed Cargo.lock.

v0.2.0 - 2021-09-23

Sadly, this is the first release without @jD91mZM2, so we - the current maintainers @aaronjanse & @Ma27 - would like to dedicate this release to them to make sure they're not forgotten.

Added

  • The LSP implementation now supports incremental LSP updates which means that changes in a file don't cause the full file to be transmitted to the LSP from your editor, but only a changeset. This should notably increase performance and reduce the memory footprint (from @Ma27 & @aaronjanse).

  • Support for auto-completing Nix builtins was added.

    With Nix 2.3 a hard-coded list of all builtins is provided, with Nix 2.4 also documentation and arguments are provided via nix __dump-builtins (from @Ma27).

  • The document link-operation of LSP now properly detects directories containing /default.nix. Also, the procedure was optimized (by @aaronjanse).

Changed

  • nixpkgs-fmt was updated to 1.2.0. This means that formatting Nix code via LSP produces the same result as using nixpkgs-fmt on the CLI (by @jD91mzm2).

  • The LSP now responds with MethodNotFound to unsupported operations (by @wiktorkuchta).

  • inherit-expressions and var@{ a, b, … } have proper autocompletion now (only for variables from within the same file, currently) (by @Ma27).

Special thanks

  • One of the reasons for this not being released earlier was a memory leak where we had a hard time to reliably reproduce this (and thus couldn't investigate properly).

    So, big thanks to @fufexan who helped us to finding a minimal example triggering the issue and helping us with the investigation in general.

v0.1.0 - 2020-01-12

  • Initial release.