| 5 Aug 2025 |
| isabel changed their profile picture. | 09:49:13 |
| Axel Karjalainen joined the room. | 18:48:14 |
| 6 Aug 2025 |
| vidariondr set a profile picture. | 18:31:00 |
| 7 Aug 2025 |
@mightyiam:matrix.org | https://discourse.nixos.org/t/nixpkgs-module-system-config-modules-graph/67722?u=mightyiam | 16:53:44 |
nbp | Let's see how much time it take before someone ask what is the difference between key and file. | 17:05:23 |
nbp | Now people might understand why you should not write a NixOS module within a flake, because it lacks position information.
{agenix, ...}:
{
# Using the module directly prevent the deduplication from working properly.
imports = [
agenix.nixosModules.default
];
}
| 17:11:50 |
nbp | * Now people might understand why you should not write a NixOS module within a flake.nix file, because it lacks position information.
{agenix, ...}:
{
# Using the module directly prevent the deduplication from working properly.
imports = [
agenix.nixosModules.default
];
}
| 17:12:41 |
| 8 Aug 2025 |
| 0x4A6F joined the room. | 06:31:30 |
nbp | (oh, this has been fixed a year ago in agenix) | 12:33:22 |
ibizaman | I have an option whose type is optionType. So in the config part, I define what the type actually is. Is it possible for this "instantiated" option to appear in the documentation/the manual? | 21:34:48 |
ibizaman | Right now I see the description for the optionType but not for the "instantiated" option. | 21:35:45 |
hsjobeki | I would say no. Documentation is only generated from options. Since the actual type is defined in config.
But i guess the values is then mapped into some module as option. There you could get the docs | 23:02:08 |
ibizaman | Makes sense indeed. Thanks! | 23:19:42 |
| 9 Aug 2025 |
| seapat set a profile picture. | 14:23:12 |