Is nvf overriding inputs in extraSpecialArgs intentional?
#1047
-
|
I’ve noticed that when passing my own inputs via extraSpecialArgs, they seem to get overridden. Only nvf’s inputs are available inside modules. Is this shadowing behavior intentional, or is it a bug? Minimal example: {
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
nvf.url = "github:notashelf/nvf";
hello.url = "github:NixOS/templates?dir=bash-hello";
};
outputs = {
self,
nixpkgs,
...
} @ inputs: let
forEachSystem = nixpkgs.lib.genAttrs ["x86_64-linux"];
in {
packages = forEachSystem (system: let
pkgs = inputs.nixpkgs.legacyPackages.${system};
neovimConfigured = inputs.nvf.lib.neovimConfiguration {
inherit pkgs;
extraSpecialArgs = {inherit inputs;};
modules = [
({inputs, ...}: let
inputsListStr = builtins.concatStringsSep ", " (builtins.attrNames inputs);
inputsMsg = "Inputs available in nvf module: ${inputsListStr}";
in
builtins.trace inputsMsg {
vim.extraPackages = [
inputs.hello.packages.${system}.hello
];
})
];
};
in {
default = self.packages.${system}.neovim;
neovimConfigured = neovimConfigured.neovim;
});
};
}Result: |
Beta Was this translation helpful? Give feedback.
Answered by
rice-cracker-dev
Jul 27, 2025
Replies: 1 comment 2 replies
-
|
yeah it is Line 25 in eaad512 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
no this is intentional behavior, raf asked me to bump this discussion