Robert Hensing
Robert Hensing
Might this help? https://github.com/hercules-ci/flake-parts/pull/40 Most flakes don't use `flakes` for system-enumerating attributes, but use `perSystem` instead, so I'm not certain how well the migration instructions work. Usually the goal is...
I'd also consider updating the module system to improve the error for all options that don't have a value defined for them.
Projects (TBD) might provide an alternative - https://github.com/hercules-ci/flake-parts/issues/205
> philosophy or architecture It is meant to be quite conservative and unopinionated, while extensible. This way, flake-parts has a chance of gluing together _all_ flake logic, instead of a...
Hi @hmanhng, I am sorry to be so late to respond to this issue. I try to keep up with flake-parts notifications but this one fell through the cracks somehow....
> > but "access to the local flake module scope" does not work properly. > > Could you clarify if you mean `inputs.self` and `self`. `config.flake` is all you need,...
[Documentation at flake.parts](https://flake.parts/options/flake-parts-modules)
I believe `nix flake check` does not accept `modules` yet, so I wouldn't recommend to migrate yet, but feel free to start using `modules`.
Is that still needed? Did you run into this again? If users set `inputs` (which almost certainly they do), Nix will use the attribute position to determine the file. That's...
> Currently flake modules are not able to visit `./.`. `self.outPath` is similar but it can result in infinite loops and stack overflow. It seems to work fine nowadays. Example:...