- Fix handling of non-object types when calling createRecordProxy for incomplete datapack arrays
- Fix parallel execution not correctly tracking tasks
- Fix vscode toolbar icon not using the correct size
- Migrate to new test structure
- Update dependencies
- Improve build parent keys algorithm.
- Added detection for UI templates for OmniScript when scanning for datapack parents.
- Added DataPack clone to context menu.
- Better handling of multi level Salesforce Records.
- Fix export does not correctly evaluate expression
- Improve handling of on-save-deploy events
- Added support for renaming and cloning datapacks.
- Update for compatibility with VSCode 1.36.0.
- Update vsce ignore file in an attempt to reduce final bundle size.
- Fix crash on datappack service loading whithout setting an override project file.
- Remove old datapack builder code and related test cases.
- Update Vlocity package to 1.11.1
- Patch VLocity package to avoid partial exports for datapacks with more then 10 dependencies
- Fix export from server command fails
- Add support for exporting all datapacks of a particular type through datapack explorer.
- Expend Salesforce record Proxy
- Change logger to process entries allowing for more flexible logging
- Fix datapack explorer doesn't when there is no custom deploy YAML
- Fix open in salesforce command to not work for datapacks with versions.
- Fix export using only direct dependencies is treated as cancellation.
- Fix
validate
not being called when a command was invoked through theCommandExecutor
- Fix error stack not logged for exceptions
- Update vlocity tools to 1.10.0
- Change code to use new
@salesforce/core
libraries instead ofSalesforce-ALM
where possible - Refactor select org command to use
@salesforce/core
- Refactor Vlocity service to provide salesforce connections from a central location
- Support for Custom datapacks defined in custom options YAML file
- Sort datapacks alphabetically in datapack explorer
- Open in Salesforce opened all pages in classic
- Open in Salesforce would not always work properly using the frontdoor session ID; for now avoid using the frontdoor.jsp
- Fix bug in switch org command causing null error.
- Prevent log to take focus for each line written; instead only focus on command start.
- Build parent key command
- Admin commands from Command Pallet
- Better detection of datapack types
- Update vlocity tools to 1.9.4
- Update all dependent packages to their latest releases available from NPM
- Update vlocity tools to 1.7.11
- Update all dependent packages to their latest releases available from NPM
- Update vlocity tools to 1.7.9
- Set dependency level when doing manual export to all, none or direct which will export related object
- Opimize plugin packeging
- Fixed critical security issue due malicious dependency in event-stream referenced by dependency
- Optimize and compress output using TerserPlugin
- Update to latest stable version of Vlocity build tools (1.7.8)
- Auto select currently open file as argument for the to be executed command instead of throwing an error.
- Handling of rejected APEX errors
- Support for loading custom override definitions
- Option to automatically activate deployed datapacks; default is on
- Datapack explorer allowing you to explore and export all datapack enabled objects available in the connect org
- Simplified setup using SFDX for authorizing new orgs and setting up the deployment tools
- New status bar org switcher making it easy to change your deployment or export target during development
- Deploy command did not work after running an export
- Configuration changes did not reload the extension config causing settings to only reflect after a VSCode restart
- Ability to export non-existing datapacks directly from within VSCode.
- Better logging to the console; disabled verbose mode by default
- Do not create new instances of the Vlocity build tools for every operation, prevents excessive logging
- Resolving datapack types based on folder structure
- Child items can now be resolved back to their parent datapack
- Checks to ensure all selected files are part of a datapack
- Do not take input focus while logging, this fixes a rather nasty behavior when editing extensions config
- Support for deploying of datapacks from within VSCode
- Preview/framework AngularJS UI for viewing datapacks
- Improved response handling for Vlocity tools results
- Build system now uses Webpack for generating extension js files
- Initial release of Vlocode with support for refreshing datapacks from the context menu.
- Enabled login using SFDX
- Use official Vlocity NPM package