!wfudwzqQUiJYJnqfSY:nixos.org

NixOS Module System

180 Members
39 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
17 Apr 2024
@ibizaman:matrix.orgibizaman Aaah yes. Got it. I agree I missed something to do that a few times. My only way is like you said, to use the module somewhere else and run nix build on it or something 14:34:04
@ibizaman:matrix.orgibizaman * Aaah yes. Got it. I agree. I missed something to do that a few times. My only way is like you said, to use the module somewhere else and run nix build on it or something 14:34:28
@JoelMcCracken:matrix.orgJoelMcCracken joined the room.16:28:10
@djacu:matrix.orgdjacu
In reply to @nbp:mozilla.org
djacu: That might be one of the most in-depth module presentation I've seen which does not present mkIf.
hah thanks! If I had more time, mkIf would have probably been the next topic.
Also link to all the lessons if you want to share -> https://nixos-modules.nix.みんな/
19:40:02
18 Apr 2024
@nbp:mozilla.orgnbp I guess, I might be completely biais into introducing mkIf early, as it feels like a must have for implementing modules in NixOS, but I think your plan might actually make more sense from a user point of view and might be better to target non-developer, who might appreciate the lack of conditional. 00:44:32
@nbp:mozilla.orgnbp * I guess, I might be completely biais into introducing mkIf early, as it feels like a must have for implementing modules in NixOS. On the other hand I think your plan might actually make more sense from a user point of view and might be better to target non-developer, who might appreciate the lack of conditional. 00:45:09
@djacu:matrix.orgdjacu
In reply to @nbp:mozilla.org
I guess, I might be completely biais into introducing mkIf early, as it feels like a must have for implementing modules in NixOS. On the other hand I think your plan might actually make more sense from a user point of view and might be better to target non-developer, who might appreciate the lack of conditional.

I'd say everything I have in the "Getting Started" section must come first as it lays the foundation for how a module can be created. Anything after that is fair game.

Does documentation need to come so early? Nah but it's a quick one and a good thing to reinforce that people should document their modules well.

I had the types section in there because I wanted to get to submodules as it is the most ubiquitous and a very powerful type.

mkIf could probably go next; it was in the Future section. I was putting lessons there that I wanted to talk about soon.

02:05:29
@djacu:matrix.orgdjacu The only issue I see with introducing mkIf early is that there needs to be a sufficient foundation so that you don't introduce anything extra. All the lessons are in an order such that only 1 or 2 new things are introduced. My hope is that this keeps the reader focused on what is currently trying to be taught and they don't have to juggle any extra information in their head. 02:07:23
19 Apr 2024
@hexa:lossy.networkhexa infinisil: https://github.com/NixOS/nixpkgs/pull/305334#issuecomment-2067069655 can you answer this? 18:44:37
@infinisil:matrix.orginfinisil
In reply to @hexa:lossy.network
infinisil: https://github.com/NixOS/nixpkgs/pull/305334#issuecomment-2067069655 can you answer this?
☑️
18:50:31
@hexa:lossy.networkhexathansk!18:50:36
@hexa:lossy.networkhexa * thanks!18:50:41
22 Apr 2024
@djacu:matrix.orgdjacu

Is there a way I can circumvent the The option <option> is used but not defined error? I am playing around with a silly idea of nix modules to html. You can see the code for the <a> tag module here: https://github.com/djacu/nix2html/blob/main/a.nix

Two attributes I've implemented so far are download and href. If you run the run.sh script, you get an output that should look like this "<a download=new-filename href=#top></a>". But I don't want a user to have to set the download or href attributes every time.

Trying to think of a good solution but coming up empty. Any ideas?

06:19:34
@infinidoge:matrix.orgMigrated to @infinidoge:inx.moeYou probably want either the anything option type, or to define your own types08:29:40
@nbp:mozilla.orgnbpWhy using submodules if you have only a single instance of each attribute?10:28:26
@nbp:mozilla.orgnbpYou can declare options to be unused: https://github.com/NixOS/nixpkgs/blob/8e54038847aa80ee2b1ffa9e313b0ab918f1903c/lib/options.nix#L228-L244 But I do not think this answer your problem. One example of usage of it is from this PR: https://github.com/NixOS/nixpkgs/pull/152785/files10:36:38
@nbp:mozilla.orgnbp Maybe you can use the type nullOr and have a default value of null. 10:37:54
@nbp:mozilla.orgnbp mkDefault should be delayed, like mkIf, so mapAttrs (name: mkDefault) should be replaceable by mkDefault.
https://github.com/NixOS/nixpkgs/blob/master/lib/modules.nix#L882
12:24:56

Show newer messages


Back to Room ListRoom Version: 10