Skip to content
New issue

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

Using mkRenamedOptionModule does not show a warning #259

Open
oddlama opened this issue Nov 25, 2024 · 0 comments
Open

Using mkRenamedOptionModule does not show a warning #259

oddlama opened this issue Nov 25, 2024 · 0 comments

Comments

@oddlama
Copy link

oddlama commented Nov 25, 2024

I'm just about to rename an option in one of my projects that have a module for flake-parts, and naturally I imported an (mkRenamedOptionModule ["agenix-rekey" "nodes" ] [ "agenix-rekey" "nixosConfigurations"]) in the relevant file. To my surprise using the old option does not trigger any warnings to be shown.

It looks like the trace gets triggered by the option type's use function, but for some reason this is not triggering when I evaluate the flake. Is there anything obvious I'm missing? It's used in a perSystem context like this:

perSystem = flake-parts-lib.mkPerSystemOption (
  { lib, ... }:
  {
    imports = [
      (lib.mkRenamedOptionModule [ "agenix-rekey" "nodes" ] [ "agenix-rekey" "nixosConfigurations" ] )
    ];
    options = {
      # ...
    };
  }
);
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant