mkdocstrings-matlab 2.1.1__tar.gz → 2.1.2__tar.gz

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/.github/workflows/docs.yaml

@@ -38,7 +38,7 @@ jobs:
           ref: ${{ inputs.ref }}
 
       - name: Install the latest version of uv
-        uses: astral-sh/setup-uv@v10.0.1
+        uses: astral-sh/setup-uv@v10.2.0
         with:
           version: "latest"
 

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/.github/workflows/qualify.yaml

@@ -73,7 +73,7 @@ jobs:
         uses: actions/checkout@v7
 
       - name: Set up uv
-        uses: astral-sh/setup-uv@v10.0.1
+        uses: astral-sh/setup-uv@v10.2.0
         with:
           version: "latest"
 

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/.github/workflows/release.yaml

@@ -49,7 +49,7 @@ jobs:
           private-key: ${{ secrets.APP_PRIVATE_KEY }}
 
       - name: Install the latest version of uv
-        uses: astral-sh/setup-uv@v10.0.1
+        uses: astral-sh/setup-uv@v10.2.0
         with:
           version: "latest"
 

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/.gitignore

@@ -141,6 +141,9 @@ venv.bak/
 # mkdocs documentation
 /site
 
+# inline-snapshot
+test/snapshots/files_using_external.txt
+
 # mypy
 .mypy_cache/
 .dmypy.json

mkdocstrings_matlab-2.1.2/.rumdl.toml

@@ -0,0 +1,72 @@
+# rumdl configuration file
+
+# Inherit settings from another config file (relative to this file's directory)
+# extends = "../base.rumdl.toml"
+
+# Global configuration options
+[global]
+
+flavor = "mkdocs"
+
+# List of rules to disable (uncomment and modify as needed)
+disable = ["MD013", "MD033", "MD041"]
+
+# List of rules to enable exclusively (replaces defaults; only these rules will run)
+# enable = ["MD001", "MD003", "MD004"]
+
+# Additional rules to enable on top of defaults (additive, does not replace)
+# Use this to activate opt-in rules like MD060, MD063, MD072, MD073, MD074
+# extend-enable = ["MD060", "MD063"]
+
+# Additional rules to disable on top of the disable list (additive)
+# extend-disable = ["MD041"]
+
+# List of file/directory patterns to include for linting (if provided, only these will be linted)
+# include = [
+#    "docs/*.md",
+#    "src/**/*.md",
+#    "README.md"
+# ]
+
+# List of file/directory patterns to exclude from linting
+exclude = [
+    # Common directories to exclude
+    ".git",
+    ".github",
+    "node_modules",
+    "vendor",
+    "dist",
+    "build",
+
+    # Specific files or patterns
+    "CHANGELOG.md",
+    "LICENSE.md",
+]
+
+# Respect .gitignore files when scanning directories (default: true)
+respect-gitignore = true
+
+# Markdown flavor/dialect (uncomment to enable)
+# Options: standard (default), gfm, commonmark, mkdocs, mdx, pandoc, quarto, obsidian, kramdown, azure_devops, myst, mdg
+# flavor = "mkdocs"
+
+# Rule-specific configurations (uncomment and modify as needed)
+
+# [MD003]
+# style = "atx"  # Heading style (atx, atx_closed, setext)
+
+# [MD004]
+# style = "asterisk"  # Unordered list style (asterisk, plus, dash, consistent)
+
+# [MD007]
+# indent = 4  # Unordered list indentation
+
+# [MD013]
+# line-length = 100  # Line length
+# code-blocks = false  # Exclude code blocks from line length check
+# tables = false  # Exclude tables from line length check
+# headings = true  # Include headings in line length check
+
+# [MD044]
+# names = ["rumdl", "Markdown", "GitHub"]  # Proper names that should be capitalized correctly
+# code-blocks = false  # Check code blocks for proper names (default: false, skips code blocks)

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: mkdocstrings-matlab
-Version: 2.1.1
+Version: 2.1.2
 Summary: A MATLAB handler for mkdocstrings
 Author-email: Mark Hu <watermarkhu@gmail.com>
 License: MIT

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/docs/api.md

@@ -11,4 +11,3 @@
       members:
         - handler
         - config
-

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/docs/index.md

@@ -5,7 +5,7 @@ hide:
 
 --8<-- "README.md:header"
 
-## Preview 
+## Preview
 
 Let's us quickly see how auto-documentation works with mkdocstrings-matlab:
 
@@ -38,10 +38,10 @@ Given the function above, the rendered documentation here is created from the fo
 
 !!! note
 
-    Syntax highlighting of argument blocks will be incorrect with the default configuration due to the outdated MATLAB lexer in [Pygments](https://github.com/pygments/pygments/) and will be resolved after [our PR](https://github.com/pygments/pygments/pull/2887) is merged. 
+    Syntax highlighting of argument blocks will be incorrect with the default configuration due to the outdated MATLAB lexer in [Pygments](https://github.com/pygments/pygments/) and will be resolved after [our PR](https://github.com/pygments/pygments/pull/2887) is merged.
 
     In the meantime, the correct syntax highlighing can be configured by adding our branch as the dependency in `pyproject.toml`
-    
+
     ```toml title="pyproject.toml"
     dependencies = [
         "pygments @ git+https://github.com/watermarkhu/pygments.git@matlab",

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/docs/license-page.md

@@ -7,6 +7,6 @@ hide:
 
 # License
 
-```
+```text
 --8<-- "LICENSE"
 ```

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/docs/src/snippets/+module/module.md

@@ -23,7 +23,7 @@
         ```matlab
         --8<-- "docs/src/snippets/+module/do_something.m"
         ```
-    
+
     === ":material-file-code: `aClass.m`"
 
         ```matlab
@@ -40,4 +40,4 @@
 
         ```matlab
         --8<-- "docs/src/snippets/+module/+submodule/Contents.m"
-        ```
+        ```

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/docs/src/snippets/+mymembers/mymembers.md

@@ -15,7 +15,7 @@
         ```matlab
         --8<-- "docs/src/snippets/+mymembers/Contents.m"
         ```
-    
+
     === ":material-file-code: `ThisClass.m`"
 
         ```matlab
@@ -32,4 +32,4 @@
 
         ```matlab
         --8<-- "docs/src/snippets/+mymembers/this_function.m"
-        ```
+        ```

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/docs/src/snippets/+mynamespace/mynamespace.md

@@ -23,7 +23,7 @@
         ```matlab
         --8<-- "docs/src/snippets/+mynamespace/classA.m"
         ```
-    
+
     === ":material-file-code: `classB.m`"
 
         ```matlab

mkdocstrings_matlab-2.1.2/docs/src/snippets/+mynamespace/readme.md

@@ -0,0 +1 @@
+This is the docstring for mynamespace.

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/docs/src/snippets/+undocumented/undocumented.md

@@ -14,7 +14,7 @@
         ```matlab
         --8<-- "docs/src/snippets/+undocumented/ClassWithoutDocstring.m"
         ```
-    
+
     === ":material-file-code: `function_with_docstring.m`"
 
         ```matlab

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/docs/usage/configuration/docstrings.md

@@ -51,13 +51,13 @@ Possible values:
         ```matlab
         function message = greet(name)
             % Greet someone.
-            %  
+            %
             % Parameters:
             %     name: The name of the person to greet.
-            % 
+            %
             % Returns:
             %     message: A greeting message.
-            
+
             message = sprintf("Hello %s!", name)
         end
         ```
@@ -67,17 +67,17 @@ Possible values:
         ```matlab
         function message = greet(name)
             % Greet someone.
-            %  
+            %
             % Parameters
             % ----------
             % name
             %    The name of the person to greet.
-            % 
+            %
             % Returns
             % -------
             % message
             %    A greeting message.
-            
+
             message = sprintf("Hello %s!", name)
         end
         ```
@@ -87,10 +87,10 @@ Possible values:
         ```matlab
         function message = greet(name)
             % Greet someone.
-            %  
+            %
             % :param name: The name of the person to greet.
             % :return: A greeting message.
-            
+
             message = sprintf("Hello %s!", name)
         end
         ```
@@ -107,7 +107,7 @@ The options for the docstring parser.
 
 The Sphinx style does not offer any option.
 
-Most of the options in the linked pages will not have an effect to mkdocstrings-matlab, since here the objects are mocked as Python objects are docstrings are injected into the mocked objects. 
+Most of the options in the linked pages will not have an effect to mkdocstrings-matlab, since here the objects are mocked as Python objects are docstrings are injected into the mocked objects.
 
 === "mkdocs.yml"
 
@@ -176,7 +176,6 @@ Sections are parsed as structured data and can therefore be rendered in differen
 
 ???+ preview
 
-
     === "Table"
 
         Tables work well when you have lots of items with short names, type annotations, descriptions, etc.. With longer strings, the columns risk getting squished horizontally. In that case, the Spacy tables can help.
@@ -233,25 +232,24 @@ Sections are parsed as structured data and can therefore be rendered in differen
 
 Whether to load inputs and output parameters based on argument validation blocks.
 
-Similarly to Python, MATLAB is by default not a typed language. Function and method arguments are dynamically typed, in most cases. This provides flexibility, but is generally bad behavior if the code is meant for production or is intended to be exposed as an API. 
+Similarly to Python, MATLAB is by default not a typed language. Function and method arguments are dynamically typed, in most cases. This provides flexibility, but is generally bad behavior if the code is meant for production or is intended to be exposed as an API.
 
-In MATLAB R2019b the concept of [Argument Definitions](https://mathworks.com/help/matlab/input-and-output-arguments.html) was introduced. Within an [arguments](https://mathworks.com/help/matlab/ref/arguments.html) block, the type, size, or other aspects of the inputs (and outputs since R2022b) can be verified. 
+In MATLAB R2019b the concept of [Argument Definitions](https://mathworks.com/help/matlab/input-and-output-arguments.html) was introduced. Within an [arguments](https://mathworks.com/help/matlab/ref/arguments.html) block, the type, size, or other aspects of the inputs (and outputs since R2022b) can be verified.
 
 ```matlab
 function z = mySharedFunction(x,y,NameValueArgs)
    arguments
       x (1,1) double     % scalar
-      y double {mustBeVector,mustBePositive} 
+      y double {mustBeVector,mustBePositive}
       NameValueArgs.A string
       NameValueArgs.B string = "default"
-   end 
+   end
 ...
 end
 ```
 
 The mkdocstrings-matlab plugin is able to parse the argument blocks and extract the type and default information, and any comment after each Argument Definition will be parsed as the argument docstring. If if `parse_arguments` is enabled, sections will be rendered for the parameters, name-value pairs and the return arguments of functions and methods. These sections can be individually toggled with [`show_docstring_input_arguments`][], [`show_docstring_name_value_arguments`][] and [`show_docstring_output_arguments`][].
 
-
 === "mkdocs.yml"
 
     ```yaml
@@ -306,7 +304,7 @@ The mkdocstrings-matlab plugin is able to parse the argument blocks and extract
 
 !!! note
 
-    Prior to MATLAB R2019b, the functionality of the arguments blocks was most commonly achieved through [`inputParser`](https://mathworks.com/help/matlab/ref/inputparser.html). The validations created with `inputParser` will not be parsed by mkdocstrings-matlab, since it does not have a strict syntax as opposed to Argument Definitions. 
+    Prior to MATLAB R2019b, the functionality of the arguments blocks was most commonly achieved through [`inputParser`](https://mathworks.com/help/matlab/ref/inputparser.html). The validations created with `inputParser` will not be parsed by mkdocstrings-matlab, since it does not have a strict syntax as opposed to Argument Definitions.
 
 ### Name-value arguments from class properties
 
@@ -349,7 +347,7 @@ The name-value argument is parsed with the struct name (`opts`) as the argument
 
 Whether to merge the constructor method into the class' signature and docstring.
 
-By default, only the class name is rendered in headings. When merging, the constructor method parameters are added after the class name, like a signature, and the constructor method docstring is appended to the class' docstring. 
+By default, only the class name is rendered in headings. When merging, the constructor method parameters are added after the class name, like a signature, and the constructor method docstring is appended to the class' docstring.
 
 === "mkdocs.yml"
 
@@ -405,14 +403,12 @@ By default, only the class name is rendered in headings. When merging, the const
               merge_constructor_into_class: false
               parse_arguments: true
         ```
-        
+
         ::: Thing
             options:
               merge_constructor_into_class: false
               parse_arguments: true
 
-
-
 ## `show_if_no_docstring`
 
 - **:octicons-package-24: Type [`bool`][] :material-equal: `False`{ title="default value" }**
@@ -471,7 +467,7 @@ With this option you can tell the Python handler to skip the docstring check.
             options:
               show_if_no_docstring: false
         ```
-        
+
         ::: +undocumented
             options:
               show_if_no_docstring: false
@@ -689,7 +685,6 @@ Whether to render the "Classes" sections of docstrings.
               show_docstring_classes: false
               members: false
 
-
 ## `show_docstring_namespaces`
 
 - **:octicons-package-24: Type [`bool`][] :material-equal: `True`{ title="default value" }**
@@ -856,7 +851,7 @@ Whether to render the "Examples" sections of docstrings.
 ???+ preview
 
     === "With examples"
-        
+
         ```markdown
         ::: print_hello
             options:
@@ -884,7 +879,7 @@ Whether to render the "Examples" sections of docstrings.
 - **:octicons-package-24: Type [`bool`][] :material-equal: `True`{ title="default value" }**
 <!-- - **:octicons-project-template-24: Template :material-null:** (N/A) -->
 
-Whether to render the "Parameters" sections of docstrings. The accepted title headings are `inputs` or `input arguments` (case-insensitive). 
+Whether to render the "Parameters" sections of docstrings. The accepted title headings are `inputs` or `input arguments` (case-insensitive).
 
 === "mkdocs.yml"
 
@@ -925,7 +920,7 @@ Whether to render the "Parameters" sections of docstrings. The accepted title he
             options:
               show_docstring_input_arguments: true
         ```
-        
+
         ::: do_something
             options:
               show_docstring_input_arguments: true
@@ -951,7 +946,7 @@ Whether to render the "Parameters" sections of docstrings. The accepted title he
 - **:octicons-package-24: Type [`bool`][] :material-equal: `True`{ title="default value" }**
 <!-- - **:octicons-project-template-24: Template :material-null:** (N/A) -->
 
-Whether to render the "Name-value pairs" sections of docstrings. The accepted title headings are `name-value pairs` or `name-value arguments` (case-insensitive). 
+Whether to render the "Name-value pairs" sections of docstrings. The accepted title headings are `name-value pairs` or `name-value arguments` (case-insensitive).
 
 === "mkdocs.yml"
 
@@ -992,7 +987,7 @@ Whether to render the "Name-value pairs" sections of docstrings. The accepted ti
             options:
               show_docstring_name_value_arguments: true
         ```
-        
+
         ::: do_varargin
             options:
               show_docstring_name_value_arguments: true
@@ -1018,7 +1013,7 @@ Whether to render the "Name-value pairs" sections of docstrings. The accepted ti
 - **:octicons-package-24: Type [`bool`][] :material-equal: `True`{ title="default value" }**
 <!-- - **:octicons-project-template-24: Template :material-null:** (N/A) -->
 
-Whether to render the "Returns" sections of docstrings. The accepted title headings are `outputs` or `output arguments` (case-insensitive). 
+Whether to render the "Returns" sections of docstrings. The accepted title headings are `outputs` or `output arguments` (case-insensitive).
 
 === "mkdocs.yml"
 
@@ -1059,7 +1054,7 @@ Whether to render the "Returns" sections of docstrings. The accepted title headi
             options:
               show_docstring_output_arguments: true
         ```
-        
+
         ::: do_output
             options:
               show_docstring_output_arguments: true

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/docs/usage/configuration/general.md

@@ -43,7 +43,7 @@ Show the base classes of a class.
 
 ???+ preview
 
-    === "with bases" 
+    === "with bases"
 
         ```markdown
         ::: myClass
@@ -56,7 +56,7 @@ Show the base classes of a class.
                 show_bases: true
 
     === "without bases"
-        
+
         ```markdown
         ::: myClass
             options:
@@ -69,13 +69,12 @@ Show the base classes of a class.
 
 ## `show_inheritance_diagram`
 
-
 - **:octicons-package-24: Type [`bool`][] :material-equal: `False`{ title="default value" }**
 <!-- - **:octicons-project-template-24: Template :material-null:** (contained in [`class.html`][class template]) -->
 
 Show the inheritance diagram of a class using [Mermaid](https://mermaid.js.org/).
 
-With this option enabled, an inheritance diagram (as a flowchart) will be displayed after a class  signature. Each node will act as a cross-reference and will bring you to the relevant class' documentation when clicking on it.
+With this option enabled, an inheritance diagram (as a flowchart) will be displayed after a class signature. Each node will act as a cross-reference and will bring you to the relevant class' documentation when clicking on it.
 
 It should work out of the box with [Material for MkDocs](https://squidfunk.github.io), but it is recommended to follow the [setup guide](https://squidfunk.github.io/mkdocs-material/reference/diagrams/#other-diagram-types) for optimal support in Material for Mkdocs. For other themes, you must either setup [mkdocs-mermaid2](https://mkdocs-mermaid2.readthedocs.io/en/latest), or include Mermaid's Javascript code manually:
 
@@ -166,8 +165,8 @@ Show the source code of this object.
 
 ???+ preview
 
-    === "with source" 
-        
+    === "with source"
+
         ```markdown
         ::: myfunction
             options:

{mkdocstrings_matlab-2.1.1 → mkdocstrings_matlab-2.1.2}/docs/usage/configuration/headings.md

@@ -15,7 +15,7 @@ When injecting documentation for an object, the object itself and its members ar
 
 The initial heading level will be used for the first layer. If you set it to 3, then headings will start with `<h3>`.
 
-If the [heading for the root object][show_root_heading] is not shown, then the initial heading level is used for its members.
+If the [heading for the root object](#show_root_heading) is not shown, then the initial heading level is used for its members.
 
 === "mkdocs.yml"
 
@@ -43,7 +43,7 @@ If the [heading for the root object][show_root_heading] is not shown, then the i
 
 --8<-- "docs/src/snippets/+mynamespace/mynamespace.md"
 
-???+ preview 
+???+ preview
 
     === "With level 3 and root heading"
 
@@ -66,7 +66,6 @@ If the [heading for the root object][show_root_heading] is not shown, then the i
         <h4><code>myfunction</code> (4)</h4>
         <p>Docstring of the function.</p>
 
-
 ## `argument_headings`
 
 - **:octicons-package-24: Type [`bool`][] :material-equal: `False`{ title="default value" }**
@@ -178,7 +177,6 @@ The identifier used in the permalink and inventory is of the following form: `pa
     <code class="doc-symbol doc-symbol-toc doc-symbol-function"></code> typed_function<br>
     <code class="doc-symbol doc-symbol-toc doc-symbol-argument" style="margin-left: 16px;"></code> input
 
-
 ## `show_root_heading`
 
 - **:octicons-package-24: Type [`bool`][] :material-equal: `False`{ title="default value" }**
@@ -223,7 +221,7 @@ Sparing that extra level can be helpful when your objects tree is deeply nested
 ???+ preview
 
     === "With root heading"
-    
+
         ::: mynamespace.classA
             options:
               show_root_heading: true
@@ -234,7 +232,7 @@ Sparing that extra level can be helpful when your objects tree is deeply nested
               members: true
 
     === "Without root heading"
-    
+
         ::: mynamespace.classA
             options:
               show_root_heading: false
@@ -250,7 +248,7 @@ Sparing that extra level can be helpful when your objects tree is deeply nested
 
 If the root heading is not shown, at least add a ToC entry for it.
 
-If you inject documentation for an object in the middle of a page, after long paragraphs, and without showing the [root heading][show_root_heading], then you will not be able to link to this particular object as it won't have a permalink and will be "lost" in the middle of text. In that case, it is useful to add a hidden anchor to the document, which will also appear in the table of contents.
+If you inject documentation for an object in the middle of a page, after long paragraphs, and without showing the [root heading](#show_root_heading), then you will not be able to link to this particular object as it won't have a permalink and will be "lost" in the middle of text. In that case, it is useful to add a hidden anchor to the document, which will also appear in the table of contents.
 
 In other cases, you might want to disable the entry to avoid polluting the ToC. It is not possible to show the root heading *and* hide the ToC entry.
 
@@ -296,10 +294,12 @@ More text.
               show_root_toc_entry: true
         ```
 
-        **Table of contents**  
-        [Some heading](#permalink-to-some-heading){ title="#permalink-to-some-heading" }  
-        [`matlab_callable`](#permalink-to-object){ title="#permalink-to-object" }   
-        [Other heading](#permalink-to-other-heading){ title="#permalink-to-other-heading" } 
+        <!-- rumdl-disable -->
+        **Table of contents**
+        [Some heading](#permalink-to-some-heading){ title="#permalink-to-some-heading" }
+        [`matlab_callable`](#permalink-to-object){ title="#permalink-to-object" }
+        [Other heading](#permalink-to-other-heading){ title="#permalink-to-other-heading" }
+        <!-- rumdl-enable -->
 
     === "Without ToC entry"
 
@@ -309,9 +309,11 @@ More text.
               show_root_toc_entry: false
         ```
 
-        **Table of contents**  
-        [Some heading](#permalink-to-some-heading){ title="#permalink-to-some-heading" }  
+        <!-- rumdl-disable -->
+        **Table of contents**
+        [Some heading](#permalink-to-some-heading){ title="#permalink-to-some-heading" }
         [Other heading](#permalink-to-other-heading){ title="#permalink-to-other-heading" }
+        <!-- rumdl-enable -->
 
 ## `show_root_full_path`
 
@@ -383,7 +385,7 @@ With this option you can choose to show the full path of the object you inject d
 
 Show the full namespace path of the root members.
 
-This option does the same thing as [`show_root_full_path`][], but for direct members  of the root object instead of the root object itself.
+This option does the same thing as [`show_root_full_path`][], but for direct members of the root object instead of the root object itself.
 
 To show the full path for every member recursively, see [`show_object_full_path`][].
 
@@ -496,7 +498,7 @@ True                          | True                    | Full
               show_docstring_output_arguments: false
 
     === "Without object full path"
-        
+
         ```markdown
         ::: +mynamespace
             options:
@@ -514,13 +516,13 @@ True                          | True                    | Full
 - **:octicons-package-24: Type [`bool`][] :material-equal: `False`{ title="default value" }**
 <!-- - **:octicons-project-template-24: Template :material-null:** (N/A) -->
 
-When [grouped by categories][group_by_category], show a heading for each category.
+When [grouped by categories](./members.md#group_by_category), show a heading for each category.
 These category headings will appear in the table of contents,
 allowing you to link to them using their permalinks.
 
 !!! warning "Not recommended with deeply nested object"
 
-    When injecting documentation for deeply nested objects, you'll quickly run out of heading levels, and the objects at the bottom of the tree risk all getting documented using H6 headings, which might decrease the readability of your API docs. 
+    When injecting documentation for deeply nested objects, you'll quickly run out of heading levels, and the objects at the bottom of the tree risk all getting documented using H6 headings, which might decrease the readability of your API docs.
 
 === "mkdocs.yml"
 
@@ -561,7 +563,7 @@ allowing you to link to them using their permalinks.
               group_by_category: true
               show_category_heading: true
         ```
-        
+
         ::: +mynamespace
             options:
               group_by_category: true
@@ -642,7 +644,7 @@ See also [`show_symbol_type_toc`][show_symbol_type_toc].
 
         ::: docs/src/snippets
             options:
-              members: 
+              members:
                 - mynamespace
               show_symbol_type_heading: true
               show_docstring_input_arguments: false