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 or directories where the source files are located. | N/A | * |
144
-
|`--useSfdxProjectJson`| N/A | Read source directories from `sfdx-project.json` packageDirectories. Cannot be used with `--sourceDir`. |`false`| * |
145
-
|`--sfdxProjectPath`| N/A | Path to directory containing `sfdx-project.json` (defaults to current directory). Only used with `--useSfdxProjectJson`. |`process.cwd()`| No |
146
-
|`--targetDir`|`-t`| The directory where the generated files will be placed. |`docs`| No |
147
-
|`--scope`|`-p`| A list of scopes to document. Values should be separated by a space, e.g --scope global public namespaceaccessible. |`[global]`| No |
148
-
|`--customObjectVisibility`|`-v`| Controls which custom objects are documented. Values should be separated by a space. |`[public]`| No |
149
-
|`--defaultGroupName`| N/A | The default group name to use when a group is not specified. |`Miscellaneous`| No |
150
-
|`--namespace`| N/A | The package namespace, if any. If provided, it will be added to the generated files. | N/A | No |
151
-
|`--sortAlphabetically`| N/A | Sorts files appearing in the Reference Guide alphabetically, as well as the members of a class, interface or enum alphabetically. If false, the members will be displayed in the same order as the code. |`false`| No |
152
-
|`--includeMetadata `| N/A | Whether to include the file's meta.xml information: Whether it is active and the API version |`false`| No |
153
-
|`--linkingStrategy`| N/A | The strategy to use when linking to other classes. Possible values are `relative`, `no-link`, and `none`|`relative`| No |
154
-
|`--customObjectsGroupName`| N/A | The name under which custom objects will be grouped in the Reference Guide |`Custom Objects`| No |
155
-
|`--triggersGroupName`| N/A | The name under which triggers will be grouped in the Reference Guide |`Triggers`| No |
156
-
|`--lwcGroupName`| N/A | The name under which Lightning Web Components will be grouped in the Reference Guide |`Triggers`| No |
157
-
|`--includeFieldSecurityMetadata`| N/A | Whether to include the compliance category and security classification for fields in the generated files. |`false`| No |
158
-
|`--includeInlineHelpTextMetadata`| N/A | Whether to include the inline help text for fields in the generated files. |`false`| No |
141
+
| Flag | Alias | Description | Default | Required |
|`--sourceDir`|`-s`| The directory or directories where the source files are located. | N/A | * |
144
+
|`--useSfdxProjectJson`| N/A | Read source directories from `sfdx-project.json` packageDirectories. Cannot be used with `--sourceDir`. |`false`| * |
145
+
|`--sfdxProjectPath`| N/A | Path to directory containing `sfdx-project.json` (defaults to current directory). Only used with `--useSfdxProjectJson`. |`process.cwd()`| No |
146
+
|`--targetDir`|`-t`| The directory where the generated files will be placed. |`docs`| No |
147
+
|`--scope`|`-p`| A list of scopes to document. Values should be separated by a space, e.g --scope global public namespaceaccessible. |`[global]`| No |
148
+
|`--customObjectVisibility`|`-v`| Controls which custom objects are documented. Values should be separated by a space. |`[public]`| No |
149
+
|`--defaultGroupName`| N/A | The default group name to use when a group is not specified. |`Miscellaneous`| No |
150
+
|`--namespace`| N/A | The package namespace, if any. If provided, it will be added to the generated files. | N/A | No |
151
+
|`--sortAlphabetically`| N/A | Sorts files appearing in the Reference Guide alphabetically, as well as the members of a class, interface or enum alphabetically. If false, the members will be displayed in the same order as the code. |`false`| No |
152
+
|`--includeMetadata `| N/A | Whether to include the file's meta.xml information: Whether it is active and the API version |`false`| No |
153
+
|`--linkingStrategy`| N/A | The strategy to use when linking to other classes. Possible values are `relative`, `no-link`, and `none`|`relative`| No |
154
+
|`--customObjectsGroupName`| N/A | The name under which custom objects will be grouped in the Reference Guide |`Custom Objects`| No |
155
+
|`--triggersGroupName`| N/A | The name under which triggers will be grouped in the Reference Guide |`Triggers`| No |
156
+
|`--experimentalLwcSupport`| N/A | Whether to document LWC files or not. |`false`| No |
157
+
|`--lwcGroupName`| N/A | The name under which Lightning Web Components will be grouped in the Reference Guide |`Lightning Web Components`| No |
158
+
|`--includeFieldSecurityMetadata`| N/A | Whether to include the compliance category and security classification for fields in the generated files. |`false`| No |
159
+
|`--includeInlineHelpTextMetadata`| N/A | Whether to include the inline help text for fields in the generated files. |`false`| No |
159
160
160
161
> **Note:** The `*` in the Required column indicates that **one** of the source directory options must be specified:
161
162
> -`--sourceDir` (single directory or array of directories)
@@ -339,6 +340,9 @@ providing the subcommand, e.g `apexdocs markdown` or `apexdocs changelog`.
339
340
340
341
### LWC Documentation Limitations
341
342
343
+
⚠️ LWC documentation is only enabled when providing the `--experimentalLwcSupport` flag or setting the
344
+
`experimentalLwcSupport` property to `true` in the configuration file.
345
+
342
346
ApexDocs supports generating documentation for Lightning Web Components (LWC) as well, but please
0 commit comments