Work your Demandware/Salesforce Cloud code
A VS Code extension to work with Demandware/Salesforce Cloud code on Sandbox that support the Script Debugger API (SDAPI) 2.0
- Upload cartridges and watch changes
- Syntax highlight for
- Validate isml files (based on htmlhint plugin, configurable by
- Advanced support of ISML syntax
- hover information
- autocomplete tags
- auto formatting
- find Symbols
- highlighting selected tags
- Setting breakpoints
- Change variables values in running threads
- Locals scope variables via the VARIABLES panel
- View variables on hover
- Variable watches
- Console/evaluate code
- Open files trought Storefront Toolkit
- Quick open
isinclude templates and custom tags via Ctrl+Click (as links)
- Cartridges overview in explorer
- Server logs viewer with syntax highlight
- Multi-root Workspaces (allows to work with different repo in same time).
WARNING: Some users had reported that debugger completely halts sandbox. Currently, this issue is not fixed and no known steps to reproduce. If you have some info about it please share. So please, before debugger usage make sure that you have availability to restart sandbox for the case if extension halts yours.
To use this extension, you must first open the folder containing the cartridges you want to work on or one of subfolders contain folder
Using the debugger
When your launch config is set up, you can debug your project! Pick a launch config from the dropdown on the Debug pane in Code. Press the play button or F5 to start.
The extension operates in one mode - it launch an adapter that connects to sandbox. Just like when using the other debugger, you configure with a
.vscode/launch.json file in the root directory of your project. You can create this file manually, or Code will create one for you if you try to run your project, and it doesn't exist yet.
launch.json configs with
"request": "launch". You must not specify hostname and other credentials. Since they will be loaded from corresponding
"name": "Attach to Sandbox"
Other optional launch config fields
trace: When true, the adapter logs its own diagnostic info to console. This is often useful info to include when filing an issue on GitHub.
Using the uploader
Configuration for uploader should be in the
cartridges folder in a file named
dw.json (similar is used by
dwupload and is compatible witn the uploader).