Is it possible to use a naming pattern other than `/path/to/module/default.nix`?
Nobody has claimed this yet.
- Dominant language
- Nix
- Stars
- 628
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
👋 firstly – thanks for building this! (it's helped me get into Nix much faster than i thought i would. 🙂)
i'm relatively new to nix, so maybe using **/default.nix is idiomatic nix – but i'm curious if it's possible to support a scheme like... modules/homes/programs/shells/zsh.nix.
the aim of doing this is to avoid the case where you're working on multiple files (in coordination) and all you can glance is default.nix | default.nix | default.nix | .... (of course, most editors will disambiguate with parent directories, but often times these are much smaller text, thus making it less likely to be glanced.)
i'm happy to help – i'm just not sure: (1) if it's an ideally supported mode and (2) where to start (it seems like flake-utils-plus leverages **/default.nix?
(also, if this is a dupe – apologies! i didn't see anything that mirrored this, but that could just be my still growing understanding of nix. 😅)
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 by examining how the current **/default.nix convention is used and how flake-utils-plus is involved. Determine whether a path such as modules/homes/programs/shells/zsh.nix can be supported, and define the expected behavior for both naming schemes.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100