Exposing `nix.generateRegistryFromInputs` and `nix.generateNixPathFromInputs`
Nobody has claimed this yet.
- Dominant language
- Nix
- Stars
- 628
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
Hey, snowfall uses flake-utils-plus internally. I love snowfall, but I quite like also having no channels as I've already had hyprland break once for no reason when rebuilding since it pulled the wrong version from my channel. Can these options (including nix.linkInputs) be exposed in snowfall too? I already made my own module that does the same in my system but I think having it in snowfall would be a better option
Snowfall doesn't actually need to do anything special, just needs to set these options depending on what the user sets in mkFlake
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the mkFlake entry point and inspect how user-provided options are passed into the flake configuration. Verify how nix.generateRegistryFromInputs, nix.generateNixPathFromInputs, and nix.linkInputs should be exposed, then confirm that each can be set through mkFlake as requested.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100