update-script/rust-analyzer: Filter out headers from option descriptions

Headers are not allowed in nixpkgs option descriptions.

generated/rust-analyzer.nix

@@ -1987,14 +1987,17 @@
   };
   "rust-analyzer.workspace.discoverConfig" = {
     description = ''
-      Enables automatic discovery of projects using [`DiscoverWorkspaceConfig::command`].
+      Enables automatic discovery of projects using
+      \[`DiscoverWorkspaceConfig::command`\].
 
-      [`DiscoverWorkspaceConfig`] also requires setting `progress_label` and `files_to_watch`.
+      \[`DiscoverWorkspaceConfig`\] also requires setting `progress_label` and
-      `progress_label` is used for the title in progress indicators, whereas `files_to_watch`
+      `files_to_watch`. `progress_label` is used for the title in progress
-      is used to determine which build system-specific files should be watched in order to
+      indicators, whereas `files_to_watch` is used to determine which build
-      reload rust-analyzer.
+      system-specific files should be watched in order to reload
+      rust-analyzer.
 
       Below is an example of a valid configuration:
+
       ``` json
       "rust-analyzer.workspace.discoverConfig": {
               "command": [
@@ -2009,11 +2012,11 @@
       }
       ```
 
-      ## On `DiscoverWorkspaceConfig::command`
+      **On `DiscoverWorkspaceConfig::command`**
 
       **Warning**: This format is provisional and subject to change.
 
-      [`DiscoverWorkspaceConfig::command`] *must* return a JSON object
+      \[`DiscoverWorkspaceConfig::command`\] *must* return a JSON object
       corresponding to `DiscoverProjectData::Finished`:
 
       ``` norun
@@ -2070,17 +2073,17 @@
 
       Similarly, the JSON representation of `DiscoverArgument::Buildfile` is:
 
-      ```
           {
                   "buildfile": "BUILD"
           }
-      ```
 
-      `DiscoverArgument::Path` is used to find and generate a `rust-project.json`,
+      `DiscoverArgument::Path` is used to find and generate a
-      and therefore, a workspace, whereas `DiscoverArgument::buildfile` is used to
+      `rust-project.json`, and therefore, a workspace, whereas
-      to update an existing workspace. As a reference for implementors,
+      `DiscoverArgument::buildfile` is used to to update an existing
-      buck2's `rust-project` will likely be useful:
+      workspace. As a reference for implementors, buck2's `rust-project` will
+      likely be useful:
       https://github.com/facebook/buck2/tree/main/integrations/rust-project.
+
     '';
     pluginDefault = null;
     type = {

update-scripts/default.nix

@@ -25,5 +25,5 @@ lib.fix (self: {
   # Derivations that build the generated files
   efmls-configs-sources = pkgs.callPackage ./efmls-configs.nix { };
   none-ls-builtins = pkgs.callPackage ./none-ls.nix { };
-  rust-analyzer-options = pkgs.callPackage ./rust-analyzer.nix { };
+  rust-analyzer-options = pkgs.callPackage ./rust-analyzer { };
 })

update-scripts/rust-analyzer/default.nix

@@ -17,6 +17,8 @@
   lib,
   rust-analyzer,
   writeText,
+  pandoc,
+  runCommand,
 }:
 let
   packageJSON = "${rust-analyzer.src}/editors/code/package.json";
@@ -132,6 +134,18 @@ let
       type ? null,
     }:
     let
+      filteredMarkdownDesc =
+        # If there is a risk that the string contains an heading filter it out
+        if lib.hasInfix "# " markdownDescription then
+          builtins.readFile (
+            runCommand "filtered-documentation" { inherit markdownDescription; } ''
+              ${lib.getExe pandoc} -o $out -t markdown \
+                --lua-filter=${./heading_filter.lua} <<<"$markdownDescription"
+            ''
+          )
+        else
+          markdownDescription;
+
       enumDesc =
         values: descriptions:
         let
@@ -140,7 +154,7 @@ let
           );
         in
         ''
-          ${markdownDescription}
+          ${filteredMarkdownDesc}
 
           Values:
           ${builtins.concatStringsSep "\n" valueDesc}
@@ -164,7 +178,7 @@ let
           enum == null && (anyOf == null || builtins.all (subProp: !(lib.hasAttr "enum" subProp)) anyOf)
         then
           ''
-            ${markdownDescription}
+            ${filteredMarkdownDesc}
           ''
         else if enum != null then
           assert lib.assertMsg (anyOf == null) "enum + anyOf types are not yet handled";

update-scripts/rust-analyzer/heading_filter.lua

@@ -0,0 +1,3 @@
+function Header(elem)
+	return pandoc.Strong(elem.content)
+end