lix/doc/manual/generate-xp-features.nix

with builtins;
with import ./utils.nix;

let
  showExperimentalFeature =
    name: doc:
    squash ''
      ## [`${name}`]{#xp-feature-${name}}

      ${doc}
    '';
in
xps: (concatStringsSep "\n" (attrValues (mapAttrs showExperimentalFeature xps)))
Assemble experimental feature docs outside of Nix itself Instead of constructing a markdown list in C++ (which involved all sorts of nasty string literals), export some JSON and assemble it with the manual build system. Besides following the precedent set with other dumped data, this is a better separate of content and presentation; if we decide for example we want to display this information in a different way, or in a different section of the manual, it will become much easier to do so. 2023-04-04 22:57:11 -04:00			`with builtins;`
			`with import ./utils.nix;`

			`let`
Format Nix code with `nixfmt` Change-Id: I61efeb666ff7481c05fcb247168290e86a250151 2024-04-04 16:07:44 -07:00			`showExperimentalFeature =`
			`name: doc:`
Single page for experimental feature descriptions As requested by @fricklerhandwerk. 2023-04-09 11:01:23 -04:00			`squash ''`
			## [`${name}`]{#xp-feature-${name}}
Assemble experimental feature docs outside of Nix itself Instead of constructing a markdown list in C++ (which involved all sorts of nasty string literals), export some JSON and assemble it with the manual build system. Besides following the precedent set with other dumped data, this is a better separate of content and presentation; if we decide for example we want to display this information in a different way, or in a different section of the manual, it will become much easier to do so. 2023-04-04 22:57:11 -04:00
Single page for experimental feature descriptions As requested by @fricklerhandwerk. 2023-04-09 11:01:23 -04:00			`${doc}`
			`'';`
Format Nix code with `nixfmt` Change-Id: I61efeb666ff7481c05fcb247168290e86a250151 2024-04-04 16:07:44 -07:00			`in`
			`xps: (concatStringsSep "\n" (attrValues (mapAttrs showExperimentalFeature xps)))`