Releases: dangmai/prettier-plugin-apex
Releases · dangmai/prettier-plugin-apex
v2.1.0
If you are upgrading from Prettier Apex v1, please follow this guide to upgrade to v2.
- Add support for Null Coalescing Expression (doc).
- Add experimental support for using native executables to speed up parsing Apex code. Follow the documentation to try it out, and please report any issues you encounter.
Internal Changes
- Use
pnpm
for internal dependency management instead ofyarn
. If you forked this repository before this change, make sure to follow CONTRIBUTING.md to set up your environment again. - This repository is now a monorepo (managed by nx), containing all packages related to this project. This change should not affect normal usage of the library, but if you are maintaining a fork of this library, please make sure to update your workflow accordingly.
- Our new Playground has been published, allowing users to try out Prettier Apex without installing anything.
- 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.1.0-rc.7
Pre-release version for v2.1.0
to test out native executable distribution
v2.0.1
v2.0.0
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.
v1.13.0
Formatting Changes
- Add support for User Mode in Database Operations (issue).
Internal Changes
start-apex-server
takes optional-c
flag, which will be passed on toapex-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.
v1.12.0
Formatting Changes
- Fix binaryish expressions having wrong indentation inside parentheses (issue).
- Keep original position for comments in between If-Else blocks and Try-Catch blocks, accordingly fix issue with unprinted comment (issue).
Internal Changes
- Use
yarn
for internal dependency management instead ofnpm
. If you forked this repository before this change, make sure to follow CONTRIBUTING.md to set up your environment again. start-apex-server
andstop-apex-server
no longer exports any methods. This should not affect any user functionality, but if you are a developer who's relying on those methods, please importstart
andstop
from http-server instead.
v1.11.0
Dependency Changes
- Drop support for NodeJS < 14
Internal Changes
- Prettier Apex has been converted to Typescript, enabling faster response time to internal jorje changes from Salesforce.
CLI Changes
- Breaking: Locations for
start-apex-server.js
andstop-apex-server.js
are changed - they are now in thedist
directory. - Add ability to specify
host
andport
options for built-in parsing server (issue).
Formatting Changes
- Add support for SOQL Geolocation Expression (issue).
- Fix SOQL Time literals always getting printed in UTC timezone.
- Fix wrong indentations inside long SELECT functions (issue).
- Remove extraneous newline at the end of long GROUP BY and WITH DATA CATEGORY clauses (issue).
- Fix unstable leading comment formatting for ternary expressions (issue).
- Add support for prettier-ignore comments in the middle of IfElseBlock (issue).
- Use user input to improve line break heuristics in short SOQL/SOSL queries (issue).
- Fix unstable leading comments before Block Statement.
- Support trailing
prettier-ignore
comments (issue). - Fix failure to call
apex-ast-serializer
because of excessively long CLASSPATH on Windows (issue). - Fix unstable end of line comments in binaryish expressions.
v1.10.0
v1.9.1
v1.9.0
Dependency Changes
- Drop support for Java < 11.
- Add support for Java 16.
Formatting Changes
- Fix SOQL query string getting quoted incorrectly in LIKE expressions (issue).
- Prefer list init syntax
new Object[0]
in certain situations (issue) - thanks to @brianmfear.