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
Copy file name to clipboardExpand all lines: README.md
+13-3Lines changed: 13 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ Here are some live projects using ApexDocs:
77
77
78
78
## 🚀 Features
79
79
80
-
* Generate documentation for Salesforce Apex classes as Markdown files
80
+
* Generate documentation for Salesforce code (Apex, triggers, custom objects, LWCs) as Markdown files
81
81
* Generate an OpenApi REST specification based on `@RestResource` classes
82
82
* Generate a changelog based on the differences between two versions of your Salesforce Apex classes
83
83
* Support for grouping blocks of related code within a class
@@ -149,10 +149,11 @@ apexdocs changelog --previousVersionDir force-app-previous --currentVersionDir f
149
149
|`--defaultGroupName`| N/A | The default group name to use when a group is not specified. |`Miscellaneous`| No |
150
150
|`--namespace`| N/A | The package namespace, if any. If provided, it will be added to the generated files. | N/A | No |
151
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 and the API version |`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
153
|`--linkingStrategy`| N/A | The strategy to use when linking to other classes. Possible values are `relative`, `no-link`, and `none`|`relative`| No |
154
154
|`--customObjectsGroupName`| N/A | The name under which custom objects will be grouped in the Reference Guide |`Custom Objects`| No |
155
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 |
156
157
|`--includeFieldSecurityMetadata`| N/A | Whether to include the compliance category and security classification for fields in the generated files. |`false`| No |
157
158
|`--includeInlineHelpTextMetadata`| N/A | Whether to include the inline help text for fields in the generated files. |`false`| No |
158
159
@@ -336,6 +337,15 @@ Then you only need to run the top level `apexdocs` command, and it will generate
336
337
Note that you can still run the individual commands if you only want to generate one type of documentation by
337
338
providing the subcommand, e.g `apexdocs markdown` or `apexdocs changelog`.
338
339
340
+
### LWC Documentation Limitations
341
+
342
+
ApexDocs supports generating documentation for Lightning Web Components (LWC) as well, but please
343
+
be aware of the following limitations:
344
+
345
+
* Only components marked as `isExposed=true` in the component's meta.xml file will be documented.
346
+
* At the moment, any JSDoc comments are ignored, documentation is based solely on the component's metadata.
347
+
* Changelog generation does not include changes to LWCs.
348
+
339
349
### Excluding Files from Being Documented
340
350
341
351
Any pattern included in the `.forceignore` file will be excluded from the documentation.
@@ -525,7 +535,7 @@ macro, and the value is a function that returns the text to inject in place of t
Copy file name to clipboardExpand all lines: examples/markdown/docs/miscellaneous/Url.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ global Url(String spec)
97
97
98
98
Creates a new instance of the URL class by parsing the specified spec within the specified context.
99
99
100
-
**Usage**
100
+
**Usage**
101
101
102
102
The new URL is created from the given context URL and the spec argument as described in RFC2396 "Uniform Resource Identifiers : Generic * Syntax" :
103
103
```xml
@@ -176,7 +176,7 @@ The authority portion of the current URL.
176
176
177
177
Returns the URL of an entire request on a Salesforce instance.
178
178
179
-
**Usage**
179
+
**Usage**
180
180
181
181
An example of a URL for an entire request is https://yourInstance.salesforce.com/apex/myVfPage.apexp.
182
182
@@ -196,7 +196,7 @@ The URL of the entire request.
196
196
197
197
Returns the default port number of the protocol associated with the current URL.
198
198
199
-
**Usage**
199
+
**Usage**
200
200
201
201
Returns -1 if the URL scheme or the stream protocol handler for the URL doesn't define a default port number.
202
202
@@ -276,15 +276,15 @@ The host name of the current URL.
276
276
277
277
Returns the canonical URL for your org. For example, https://MyDomainName.my.salesforce.com.
278
278
279
-
**Usage**
279
+
**Usage**
280
280
281
281
Use getOrgDomainUrl() to interact with Salesforce REST and SOAP APIs in Apex code. Get endpoints for User Interface API calls, for creating and customizing picklist value sets and custom fields, and more.
282
282
283
283
`getOrgDomainUrl()` can access the domain URL only for the org in which the Apex code is running.
284
284
285
285
You don't need a RemoteSiteSetting for your org to interact with the Salesforce APIs using domain URLs retrieved with this method.
286
286
287
-
**See Also**
287
+
**See Also**
288
288
289
289
*[Lightning Aura Components Developer Guide: Making API Calls from Apex](https://developer.salesforce.com/docs/atlas.en-us.250.0.lightning.meta/lightning/apex_api_calls.htm)
0 commit comments