Skip to content

Releases: neowit/tooling-force.com

v0.6.1.0

24 Jun 16:33

Choose a tag to compare

v0.6.1.0 Pre-release
Pre-release

updated default SFDC API version and salesforce libraries to v61.0

This release includes 1 jar

  • tooling-force.com-0.6.1.0-JDK11.jar - compiled with JDK 11

v0.5.8.0

18 Jun 10:52

Choose a tag to compare

v0.5.8.0 Pre-release
Pre-release
  • updated default SFDC API version to v58.0
  • updated Apex API definitions to v58, which includes new methods in Database namespace

This release includes 2 jars

  • tooling-force.com-0.5.8.0.jar - compiled with JDK 17
  • tooling-force.com-0.5.8.0-JDK11.jar - compiled with JDK 11

v0.5.1.0

13 Apr 12:54

Choose a tag to compare

v0.5.1.0 Pre-release
Pre-release
  • updated default SFDC API version to v51.0
  • updated to support scala 2.13
  • bugfixes (see commits log)

v0.4.7.0

04 Jan 17:00

Choose a tag to compare

v0.4.7.0 Pre-release
Pre-release
  • updated default SFDC API version to v47.0
  • initial suport for LWC
  • bugfixes (see commits log)

v0.4.5.0

04 Jan 17:01

Choose a tag to compare

v0.4.5.0 Pre-release
Pre-release
  • new action: "--guessSetupUrl"
  • add support for few more aura types (.svg, .design, .intf)
  • update to SFDC API v45

v0.4.4.0

07 Nov 16:54

Choose a tag to compare

v0.4.4.0 Pre-release
Pre-release
  • update to SFDC API v44 (winter 19)
  • New action: deleteLogs - removes all debug logs
  • new acton: loadApexCodeCoverageAggregate - queries code coverage detail for specified class or trigger
  • workaround for Winter 19 SFDC Bug: blank locationsNotCovered from REST: /tooling/runTestsSynchronous/

v0.4.2.0

16 Apr 15:24

Choose a tag to compare

v0.4.2.0 Pre-release
Pre-release

Syntax analysis and code completion have been rewritten from scratch - i.e. expect some regressions and new bugs in code completion.
New completion engine should significantly speed up the response time of the first completion (after server start) on large code bases. Syntax analysis should be more accurate.

In this release .jar file has not been optimised via ProGuard because current version of ProGuard causes some issues on the new code base at runtime, therefore resulting jar is much larger than previous releases.

v0.4.0.2

19 Jul 11:18

Choose a tag to compare

v0.4.0.2 Pre-release
Pre-release

another minor update to Apexcode grammar

v0.4.0.1

17 Jul 19:42

Choose a tag to compare

v0.4.0.1 Pre-release
Pre-release

minor updates to Apexcode grammar

v0.4.0.0

16 Jun 19:42

Choose a tag to compare

v0.4.0.0 Pre-release
Pre-release
  • update to SFDC API v40
  • apexcode parser and syntax check should not trip over SOSL statements like [find ... ]