Bug | Option Documents Break Nix Build #42
Merged
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.
Description
Two issue existed with the options documentation that caused build failures when
documentation.nixos.enable
anddocumentation.nixos.includeAllModules
are set totrue
.The first issue was that
mkDoc
was used rather thanlib.mdDoc
in two locations.mkDoc
isn't valid, so I replaced both instances of it withlib.mdDoc
.The second issue was that not all options of
nix-flatpak
had descriptions. This also causes a build failure.In addition to fixing the two issues above that cause build failures, I also:
README.md
.Why Wasn't it Noticed Sooner
By default
documentation.nixos.enable
istrue
anddocumentation.nixos.includeAllModules
isfalse
. The latter value used to default totrue
, but was changed due to build performance concerns for NixOps users. Having said that, there has been discussion of turning the default back totrue
for non NixOps users. If this is done, then everyone who uses this module will end up with broken system builds.In short, I noticed first because I was the first person to use this module and set
documentation.nixos.includeAllModules
totrue
.