Splitting a wrapped package's configuration into modules and importing them by name

[MATOO-Dev]

I'm currently writing a config using flake-parts and following the dendritic pattern. I'm now trying to create a wrapped niri package in a similar manner to this, but with the configuration split across multiple files, and im still struggling with importing the individual modules. Basically, I want to achieve something along the lines of this:

perSystem = { pkgs, lib, ... }: {
	packages.niri = inputs.wrapper-modules.wrappers.niri.wrap {
		inherit pkgs;
		imports = [
			self.<moduleType>.niri-autostart
			self.<moduleType>.niri-binds
			# and so on
		];
	};
};

I'm not quite sure what to put in place of <moduleType>. For nixos & home-manager configurations, i would use nixosModules and homeModules respectively, but those two doesn't apply here (I think?). Checking the documentation, on the 'getting started' page there is a section on flake-parts, which (if I'm unterstanding correctly) instructs me to instead define it like so:

flake.wrappers.niri = { pkgs, wlib, ... }: {
	imports = [ wlib.wrapperModules.niri ];
	# configuration options here
};

But at that point I'm still unsure about how to split the configuration into multiple files. I tried checking some public configs, but unfortunately that didn't really get me anywhere, and my other attempts so far resulted in infinite recursion.

[BirdeeHub]

Hmm

Yeah flake.wrappers and the exported flake.wrapperModules really do usually expect a whole wrapper module with the program and stuff

On the bright side, if the module was imported via a path, as wlib.wrapperModules.niri is in your example, it will automatically deduplicate.

So, method 1, would be put wlib.wrapperModules.niri in flake.wrappers.niri-binds and the like, and then you would also export one final niri wrapper with all of those imported via self.wrapperModules.niri-binds and such, (which get automatically created based on flake.wrappers).

But that would of course be somewhat cumbersome, as you might then want to use perSystem.wrappers.packages.niri-binds = true; to disable those from being actually built into packages and all that (if you wanted to, although you don't have to technically since they all would be importing wlib.wrapperModules.niri, they would still be buildable)

---

So, the way I would recommend is to use the flake-parts.flakeModules.modules module

and then you would flake.modules.niri.binds and flake.modules.niri.autostart and can import those.

We don't set a "class" for our wrapper module evaluation, because not all wrapper modules are importable in all other wrapper modules, so, we would want a class per program technically. It won't enforce this (unless you pass class to your call of wlib.evalModules), but flake.modules.niri.<name> would be the way to go about making modules of a "niri" class to use to compose your niri wrapper module.

[MATOO-Dev]

The flake-parts.flakeModules.modules approach is exactly what I was looking for, works great! Thanks for your help and the quick reply!