Add render.enable
and render.output
options
#1288
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow downstream users to use the render module, without adding packages to
perSystem.packages
.Motivation
In nixvim, we already have a MDBook based documentation site, similar to the flake.parts website.
We'd like to add some pages documenting flake-parts modules, so the
render
module would be useful to avoid re-implement things likeevalWith
ourselves.However we don't need/want to add the
generated-docs
packages to our flake outputs. Instead, we'd iterate overperSystem.render.inputs
ourselves, perhaps adding relevant derivations aspassthru
attrs on our main docs package.