v0.18.0 Strict Mode lacks definitions for core class types #626
Unanswered
DylanRJohnston
asked this question in
Help - Issues / Problem Solving / How To
Replies: 3 comments 2 replies
|
There was some discussion of strict by default here but it seems like that wasn't enabled otherwise everyone would be having this issue? I was also having trouble figuring out what the type should be, I think it needs to be some variation of this? Line 599 in 3932adf |
0 replies
|
Ugh, now we're back to the problem of defined options setting { denTest, ... }:
{
flake.tests.issue-xxx-user-strict-mode = {
test-user-class-works-in-strict-mode = denTest (
{
inputs,
igloo,
lib,
den,
...
}:
{
imports = [ inputs.den.flakeModules.strict ];
den.schema.aspect.options.nixos = lib.mkOption {
type = lib.types.anything;
};
den.schema.aspect.options.homeManager = lib.mkOption {
type = lib.types.anything;
};
den.schema.aspect.options.user = lib.mkOption {
type = lib.types.anything;
};
den.hosts.x86_64-linux.igloo.users.tux = { };
den.aspects.tux.user.isNormalUser = false;
expr = igloo.users.users.tux.isNormalUser;
expected = false;
}
);
};
}
|
0 replies
|
Maybe we just abandon strict mode? |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey all, finally have some time to update my Den config to v0.18.0 and I'm going through try to understand the new effect system. As fas I can tell, when
inputs.den.flakeModules.strictis enabled, none of the core class types have registered themselves with theden.schema.aspectsschema module. e.g.Is this the intended behaviour? That users type all of the core classes themselves? Or should they each respectively register their types with
den.schema.aspects?All reactions