You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| --sourceDir | -s | The directory location which contains your apex .cls classes. | N/A | Yes |
124
-
| --targetDir | -t | The directory location where documentation will be generated to. |`docs`| No |
125
-
| --recursive | -r | Whether .cls classes will be searched for recursively in the directory provided. |`true`| No |
126
-
| --scope | -p | A list of scopes to document. Values should be separated by a space, e.g --scope public private. Note that this setting is ignored if generating an OpenApi REST specification since that looks for classes annotated with @RestResource. |`global`| No |
127
-
| --targetGenerator | -g | Define the static file generator for which the documents will be created. Currently supports: `jekyll`, `docsify`, `plain-markdown`, and `openapi`. |`jekyll`| No |
128
-
| --indexOnly | N/A | Defines whether only the index file should be generated. |`false`| No |
129
-
| --defaultGroupName | N/A | Defines the `@group` name to be used when a file does not specify it. |`Miscellaneous`| No |
130
-
| --sanitizeHtml | N/A | When on, any special character within your ApexDocs is converted into its HTML code representation. This is specially useful when generic objects are described within the docs, e.g. "List< Foo>", "Map<Foo, Bar>" because otherwise the content within < and > would be treated as HTML tags and not shown in the output. Content in @example blocks are never sanitized. |`Apex REST Api`| No |
131
-
| --openApiTitle | N/A | If using "openapi" as the target generator, this allows you to specify the OpenApi title value. | true | No |
132
-
| --title | N/A | Allows you to specify the home page main title. If using "openapi" this acts as an alias to the openApiTitle parameter |`Classes`| No |
133
-
| --namespace | N/A | The package namespace, if any. If this value is provided the namespace will be added as a prefix to all of the parsed files. If generating an OpenApi definition, it will be added to the file's Server Url. | N/A | No |
134
-
| --openApiFileName | N/A | If using "openapi" as the target generator, this allows you to specify the name of the output file. |`openapi`| No |
135
-
| --includeMetadata | N/A | Whether to include the file's meta.xml information: Whether it is active and and the API version | false | No |
| --sourceDir | -s | The directory location which contains your apex .cls classes. | N/A | Yes |
124
+
| --targetDir | -t | The directory location where documentation will be generated to. |`docs`| No |
125
+
| --recursive | -r | Whether .cls classes will be searched for recursively in the directory provided. |`true`| No |
126
+
| --scope | -p | A list of scopes to document. Values should be separated by a space, e.g --scope public private. Note that this setting is ignored if generating an OpenApi REST specification since that looks for classes annotated with @RestResource. |`global`| No |
127
+
| --targetGenerator | -g | Define the static file generator for which the documents will be created. Currently supports: `jekyll`, `docsify`, `plain-markdown`, and `openapi`. |`jekyll`| No |
128
+
| --indexOnly | N/A | Defines whether only the index file should be generated. |`false`| No |
129
+
| --defaultGroupName | N/A | Defines the `@group` name to be used when a file does not specify it. |`Miscellaneous`| No |
130
+
| --sanitizeHtml | N/A | When on, any special character within your ApexDocs is converted into its HTML code representation. This is specially useful when generic objects are described within the docs, e.g. "List< Foo>", "Map<Foo, Bar>" because otherwise the content within < and > would be treated as HTML tags and not shown in the output. Content in @example blocks are never sanitized. |`Apex REST Api`| No |
131
+
| --openApiTitle | N/A | If using "openapi" as the target generator, this allows you to specify the OpenApi title value. | true | No |
132
+
| --title | N/A | Allows you to specify the home page main title. If using "openapi" this acts as an alias to the openApiTitle parameter |`Classes`| No |
133
+
| --namespace | N/A | The package namespace, if any. If this value is provided the namespace will be added as a prefix to all of the parsed files. If generating an OpenApi definition, it will be added to the file's Server Url. | N/A | No |
134
+
| --openApiFileName | N/A | If using "openapi" as the target generator, this allows you to specify the name of the output file. |`openapi`| No |
135
+
| --includeMetadata | N/A | Whether to include the file's meta.xml information: Whether it is active and and the API version | false | No |
136
+
| --documentationRootDir | N/A | The root directory where the documentation will be generated. This is useful when you want to generate the documentation in a subdirectory of your project. | N/A | No |
0 commit comments