Skip to content

Releases: IlyaMatsuev/prettier-plugin-apex

v3.0.0

03 Sep 23:12
287701a
Compare
Choose a tag to compare

Please follow this guide to upgrade Prettier Apex to this new major version.

Dependency Changes

  • Support Prettier v3 (issue). You cannot use this version with Prettier v2, please plan your upgrade accordingly.
  • Drop support for NodeJS < 18.11.0.

Internal Changes

  • Prettier Apex is now distributed as an ECMAScript Module. This shouldn't affect normal usage of the library, but if you are importing code from Prettier Apex you may need to change your code to adapt.
  • Allow user to customize the secret used to shut down the parsing server.
  • Allow user to specify the protocol (HTTP/HTTPS) that the parsing server uses.

v2.3.0

02 Jul 14:53
b09b738
Compare
Choose a tag to compare

Formatting Changes

  • Add support for User Mode in Database Operations (issue).

Dependency Changes

  • Support Prettier v3 (issue). You cannot use this version with Prettier v2, please plan your upgrade accordingly.
  • Drop support for NodeJS < 16.19.0.

v2.2.0

19 Feb 20:24
74caa0b
Compare
Choose a tag to compare

Formatting Changes

  • Add a new option apexForceCurly that allows to force curly brackets for if-else and loop blocks issue.
  • Enhance the apexFormatAnnotations option by merging it with the apexAnnotationsArgsSpacing option. The apexAnnotationsArgsSpacing option is not available separately anymore. If apexFormatAnnotation option is enabled it would also format annotation arguments to lower came case issue.
  • Make the apexFormatStandardTypes option less powerful, removing the ability to correct chained methods calls. Now, the option will only work for types in declarations. This was made to increase reliability and make the output more predictable since it was possible that the variable name would be misinterpreted and printed uppercase, for example.
  • Allow an extra line break in the beginning of the class/interface declaration issue.
  • Change the formatting behaviour for apexFormatInlineComments. It's now a choice option. Check out how it can be used in the changelog examples issue.

v2.1.1

13 Feb 23:48
Compare
Choose a tag to compare

Internal Changes

  • Fix the issue with the package installation that was caused by husky.

2.1.0

11 Feb 19:51
9787fc1
Compare
Choose a tag to compare

Internal Changes

  • start-apex-server takes optional -c flag, which will be passed on to apex-ast-serializer as a comma-delimited list of allowed origins that will be added to the CORS headers returned by the parsing server.
  • start-apex-server pipes internal logs to console, so that errors can be caught more quickly by users.

Formatting Changes

  • Fix an issue with the apexSortModifiers option which removes a method modifier if there is an own-line comment between annotation and method (issue).
  • Fix an issue with the apexExplicitAccessModifier option when all trigger variables are treated as fields, adding non needed private keyword (issue).
  • Fix an issue with the apexExplicitAccessModifier option when the webservice method gets an access modifier (issue).
  • Fix an issue with the apexExplicitAccessModifier option when the method parameters get private modifier (issue).
  • Update the apexFormatAnnotations option to convert the testmethod method modifier to the @IsTest annotation (issue).
  • Change the formatting of webservice and testmethod modifiers to be always printed in lowercase instead of webService and testMethod.