⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Type
Other
🔖 Feature description
Currently nvf puts its own flake's inputs into specialArgs, ensuring nvf modules have access to inputs they expect. But this approach means if I want to pass my own flake's inputs (via extraSpecialArgs) for use in my configuration or modules, there is no way to do so. my inputs are always overwritten.
✔️ Solution
A pattern or mechanism to make both sets of inputs accessible in modules:
- nvf’s own flake inputs (as needed by nvf itself and its modules)
- User’s own flake inputs, passed via extraSpecialArgs, for custom configuration
❓ Alternatives
No response
📝 Additional Context
No response