We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Isn't the need for such a thing a blatant code smell? Is there any upstream issues to address this?
The text was updated successfully, but these errors were encountered:
Might be.
I have raised the issue in the flake matrix chat and the Unofficial Flakes Roadmap has an idea about "input groups", which is somewhat related.
flake
I'm not sure, however, if there already is (strong) consensus that the flake.lock file should be concise / terse and not hold extra entries.
flake.lock
I think the only way to achieve this ahead of full eval time is to define input groups who correspond to an output such as:
myOutputInputs -> self.myOutput
This way, we could declare which outputs a consumer intents to use and only fetch inputs from this particular output.
On the other hand, it might be that the correct answer to "input groups", might actually be subflakes.
Sorry, something went wrong.
No branches or pull requests
Isn't the need for such a thing a blatant code smell? Is there any upstream issues to address this?
The text was updated successfully, but these errors were encountered: