In reply to @accelbread:matrix.org
maybe i can extend the option module with some sort of "import type"

This layout will not work, since with-overlays should result in a list rather than an attribute set.

Would it be possible to change Flakelight, so you can decide whether a directory should be treated as a list, rather than an attribute set?

Great! It seems to work wonderfully, when importing overlays that does not need inputs.

But how can you handle with overlays that require inputs like this?

hmm, at that point its a file expected to be an overlay. I don't know of a way to distinguish moduleArgs -> overlay from overlay. After one application, both are functions, and after two applications the overlay needs to use the params, so I need the real args.

I guess it can be deffered to overlay evaluation time like i did in bundlers. I could potentially make that work but even then, the preferred way to write that would be:

final: prev: (import prev.inputs.rust-overlay) final prev

that should already work.
I'll see if i can make the proposed y
syntax work though

Yet another idea. Supporting wildcards in the alias like this:

nixDirAliases = {
  nixosModules = [ "nixos/modules/*"]
};

So you could support the layout:

The right side can be a path, yes; problem is the left side which doesn't support nesting.
I was considering having it recurse, but even then not sure if that would work since the key is not a concrete option.

for that you could write (assuming the dirs are dirs you want to load as attrs):

devShells = {
  ansible = flakelight.importDir "ansible/nix";
  autotest = flakelight.importDir "autotest/nix";
  dbusmock = flakelight.importDir "dbus-mock/nix";
};

or as I'd more likely write:

devShells = lib.genAttrs [ "ansible" "autotest" "dbus-mock" ] (n: flakelight.importDir "${n}/nix";

The right side can be a path, yes; problem is the left side which doesn't support nesting.
I was considering having it recurse, but even then not sure if that would work since the key is not a concrete option.

for that you could write (assuming the dirs are dirs you want to load as attrs):

devShells = {
  ansible = flakelight.importDir "ansible/nix";
  autotest = flakelight.importDir "autotest/nix";
  dbusmock = flakelight.importDir "dbus-mock/nix";
};

or as I'd more likely write:

devShells = lib.genAttrs [ "ansible" "autotest" "dbus-mock" ] (n: flakelight.importDir "${n}/nix");

The right side can be a path, yes; problem is the left side which doesn't support nesting.
I was considering having it recurse, but even then not sure if that would work since the key is not a concrete option.

for that you could write (assuming the dirs are dirs you want to load as attrs):

devShells = {
  ansible = flakelight.importDir "ansible/nix";
  autotest = flakelight.importDir "autotest/nix";
  dbusmock = flakelight.importDir "dbus-mock/nix";
};

or as I'd more likely write:

devShells = lib.genAttrs
  [ "ansible" "autotest" "dbus-mock" ]
  (n: flakelight.importDir "${n}/nix");