Auto-wiring

[roberth]

Modules can provide various levels of integration, where an integration is any definition that isn't of a function that it declares.
Sometimes, integrations are not desirable. Making integrations lib.mkDefault may help, but this may not always be sufficient. If it turns out that some flakes need to disable too many integrations explicitly, perhaps it makes sense to introduce a single global option that disables all integrations. All (reusable) modules should then adhere to that option.

The story of a flake would then be

1. initialize a flake with flake-parts
2. add some modules with integrations
3. use the integrations
4. add a module with undesirable integration
5. configure that module to disable that integration (?)
6. encounter another undesirable integration
7. set autoWire = false
8. write the missing integrations that they did need

Perhaps modules could list their integrations in another option, to help with (8), but all in all it's not a great experience. I would consider this idea to be a last resort; I hope we'll find better solutions.

[srid]

I just had an use-case for granular auto-wiring: srid/haskell-flake#142

[srid]

Another: Platonic-Systems/process-compose-flake#27

[roberth]

Projects (TBD) might provide an alternative

• Per system option with a different name? #205

[srid]

Another: juspay/rust-flake#13

[srid]

Another: https://nixos-unified.org/autowiring.html