We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nixvim/plugins/lsp/language-servers/default.nix
Line 184 in c892aa2
This line errors for me on main with unstable nixpkgs.
main
unstable
Asserting that pkgs was built from the expected nixpkgs release/channel may allow us to offer more useful error messages.
pkgs
We could use lib.trivial.release (etc) to check for a compatible nixpkgs release.
lib.trivial.release
We would probably need to track somewhere in our repo what release this branch is expecting though.
Maybe this could also be used within the docs to detect if the docs relate to stable or unstable nixivm? (see #2455)
The text was updated successfully, but these errors were encountered:
Okay, the issue here was that my nixvim flake input followed the unstable channel, but the nixvimModule got the stable channel passed as pkgs.
nixvim
nixvimModule
Maybe there should be a check for this?
Sorry, something went wrong.
I can rename this issue to something like "assert that the expected nixpkgs release/channel is used"?
EDIT: done
No branches or pull requests
nixvim/plugins/lsp/language-servers/default.nix
Line 184 in c892aa2
This line errors for me on
main
withunstable
nixpkgs.EDIT by maintainers
Asserting that
pkgs
was built from the expected nixpkgs release/channel may allow us to offer more useful error messages.We could use
lib.trivial.release
(etc) to check for a compatible nixpkgs release.We would probably need to track somewhere in our repo what release this branch is expecting though.
Maybe this could also be used within the docs to detect if the docs relate to stable or unstable nixivm? (see #2455)
The text was updated successfully, but these errors were encountered: