mirror of
https://github.com/NixOS/nixpkgs.git
synced 2024-10-21 11:43:11 -04:00
4a014ed92e
The practical use for this should be very limited because I don't think anyone should change `lib`, let alone change `lib.functionArgs`, but, but it would be even stranger to rely on `args.lib` (or really `specialArgs.lib` for what's clearly a behavior of the current `evalModules`, which uses its own ambient lib for basically everything. The shadowing of `lib` by `args.lib` here seems to be a small mistake, which is easy to make.
29 lines
831 B
Nix
29 lines
831 B
Nix
{ config, lib, ... }:
|
|
|
|
{
|
|
options = {
|
|
result = lib.mkOption { };
|
|
weird = lib.mkOption {
|
|
type = lib.types.submoduleWith {
|
|
# I generally recommend against overriding lib, because that leads to
|
|
# slightly incompatible dialects of the module system.
|
|
# Nonetheless, it's worth guarding the property that the module system
|
|
# evaluates with a completely custom lib, as a matter of separation of
|
|
# concerns.
|
|
specialArgs.lib = { };
|
|
modules = [ ];
|
|
};
|
|
};
|
|
};
|
|
config.weird = args@{ ... /* note the lack of a `lib` argument */ }:
|
|
assert args.lib == { };
|
|
assert args.specialArgs == { lib = { }; };
|
|
{
|
|
options.foo = lib.mkOption { };
|
|
config.foo = lib.mkIf true "alright";
|
|
};
|
|
config.result =
|
|
assert config.weird.foo == "alright";
|
|
"ok";
|
|
}
|