Skip to content

Releases: cesarParra/apexdocs

v2.17.1

05 Oct 14:03
245b8ca
Compare
Choose a tag to compare

v2.17.0

10 Aug 20:35
accb534
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2.16.0...v2.17.0

v2.16.0

28 Jul 00:08
abf704f
Compare
Choose a tag to compare

Adds support for parsing a doc line that has multiple tags. Tags are not treated as annotations if they are wrapped in ticks (`)

for example

/**
 * @description something `@escaped` escaped
*/

What's Changed

Full Changelog: v2.15.1...v2.16.0

v2.15.1

13 Apr 21:27
b2ab83c
Compare
Choose a tag to compare

Includes fix for #81

v2.15.0

25 Mar 12:27
38d7f7d
Compare
Choose a tag to compare

Includes

A new CLI argument has been added: documentationRootDir

If your documentation documents live in a subfolder of a bigger site, use this argument to specify the path to the subfolder (relative to the root of the site), to correctly generate links between documentation files.

v2.14.0

06 Mar 22:17
976cff1
Compare
Choose a tag to compare

Includes:

v2.13.0

24 Jan 12:52
b7f5dff
Compare
Choose a tag to compare

Improvements

Support for the @ignore tag.

An @ignore tag can now be used in any ApexDoc to have the annotated code be ignored during the documentation creation process.

Improved error handling

When dealing with uncaught exceptions, the process now exits with an exit code of 1

Upgraded to use the latest version of the Apex Reflection library, which support for the latest Apex improvements introduced during Winter 23

General improvements when generating OpenApi definitions

v2.12.0

27 Dec 13:21
f070832
Compare
Choose a tag to compare

General Improvements

Upgraded to latest version of the Apex Reflection library, which now ignores ApexDoc blocks in unexpected places of the code. This should improve the noise when parsing files with regular comments throughout the source code that are not meant to be apex docs, but still use the ApexDoc comment syntax /** ... */

OpenApi Improvements

RestResource annotations ending in a wildcard character are now cleanedup during the generation of the OpenApi definition file. e.g /Accounts/* will now simply be /Accounts/

2.11.0

21 Dec 11:31
99b4ffa
Compare
Choose a tag to compare

Grouping improvements

OpenApi definition file improvements

  • When parsing an HTTP related method, if no ApexDocs are given to override the request body definition, the method's arguments will be used to form the OpenApi's request body section for that endpoint
  • Similarly, when no ApexDocs are given to override the response body, the method's return type will be used to form the response corresponding to the 200 status code.

v2.10.0

15 Dec 11:17
798fe4b
Compare
Choose a tag to compare

General updates

Namespace support

A new property has been added to allow for a package namespace to be specified. When set, the generated files will be created with the prepended namespace.

When generating an OpenApi definition, the namespace will be added to the file's server URL section, complying with how REST APIs for managed packages are exposed by Salesforce.

Upgraded to use the latest version of the Apex Reflection library

This version includes support for methods named void, which (for some reason) is allowed by Apex even though it is a keyword that should be reserved

OpenApi generator updates

Ability to specify the name of the output file through a new CLI argument

Ability to override the schema references when referencing custom classes from RestResource files.