Releases: neowit/tooling-force.com
Releases · neowit/tooling-force.com
v0.3.4.0
- API v34.0 (Summer '15)
- built against Partner/Metadata/Tooling/Apex APIs v34.0 (Summer '15)
--soqlQuery
now supports both Partner and Tooling APIs--saveModified
&--saveSpecificFiles
(using Tooling API) now support Static Resource
--- previously (if static resource is detected in the list of files "to save" then it would switch to Metadata API)- new command
--runTestsTooling
- run tests using Tooling API insync
orasync
mode
Note: there is a bug in Metadata API v34.0 (Summer '15) which may influence how code coverage is reported after --deployModified
with tests. Details here: http://salesforce.stackexchange.com/questions/84797/metadata-deploy-test-code-coverage-report-is-broken-in-metadata-api-v34-0-sum
v0.3.3.3
New
- apex auto complete for
@<annotation>
- when running in server mode use individual console log for each thread
- action: --saveSpecificFiles
Fixed
- enforce UTF-8 encoding when reading/writing files
- fall back to metadata Retrieve when can not check conflicts using SOQL
v0.3.3.2
v0.3.3.1
Apex code completion
- bugfix - improve inner class definition resolution
- when displaying completion candidates also display "javadoc" comments that go before method signature
aura
- fixed bug in determining if file is a part aura bundle
v0.3.3.0
SOQL completion
- this release contains initial version of suggesting code completion candidates in SOQL expressions - field names, date literals, aggregate functions, FROM object type, inner query FROM child relationship names, etc.
Demo here: http://youtu.be/rzqgXV3Gx0s
Apex code completion
- parser used for Apex completion is now case insensitive. Previous versions required apex keywords (e.g. "with sharing") to match the case in apex API documentation
- performance improvements for apex completion candidates in large source files
- various fixes to Apex grammar