Skip to Content

v1.0.8

New features

B2C Doctor

B2C Doctor finds what nothing in your linked cartridges uses, says why each piece is dead and whether it is safe to remove, and removes a selection at once with Undo to put it back. Click Open B2C Doctor in the title bar of the Cartridges view, or run Intellij SFCC: Open B2C Doctor from the Command Palette. See B2C Doctor.

B2C Doctor finds the files, code, routes, resource keys, hooks, tags and metadata nothing in your linked cartridges uses, says why and what is safe to remove, and removes it at once with Undo to put it back. Script editors fade the unused code and offer a quick fix to remove it
  • Overview: The findings, what is Ready to remove, what to Check first and the errors, by type and by cartridge, with the live files that have the most unused code.
  • Findings: Unused scripts, templates, forms and JSON files, unused functions, variables, requires and exports, commented-out code, routes nothing links to, resource keys, custom hooks and tags, custom attributes and custom object types. Each one says why it counts as dead and what to do, next to its code. Group them by type or by cartridge, and search them by name or path.
  • Remove: A selection goes at once, and Undo puts it all back. A resource key goes from every locale file of its bundle, and a file the server logs show running starts unticked.
  • Errors: The error-level problems in the files B2C Doctor reads, and the errors Log Center found in the server logs, at their lines.
  • In the editor: Script editors fade unused requires, functions, variables and exports, and a lens above the first line counts them, with Show in B2C Doctor, Remove All in This File... and Ignore All in This File. A dead file says why in its lens, and the light bulb offers Remove with B2C Doctor... and Ignore in B2C Doctor.
B2C Doctor finds the files, code, routes, resource keys, hooks, tags and metadata nothing in your linked cartridges uses, says why and what is safe to remove, and removes it at once with Undo to put it back. Script editors fade the unused code and offer a quick fix to remove it
  • Share: Share… turns the Overview into an image to copy or save, for a ticket or a team chat.
  • Agents: Two B2C MCP tools give AI agents the same scan. They read the counts first, then only the findings they need, and plan a removal that runs at once after you confirm it in VS Code.

B2C Doctor needs an active license or trial.

Improvements

  • .apiversion in Code Deployment: When the instance has an API version, the .apiversion file is the first row of its Code Deployment tab, with its status, size, time and request details. It goes up right after the cleanup, before any zip, and the console says 🏷️ .apiversion → uploaded: version=22.7. The deployment summary shows the compatibility mode, and the status line still counts only cartridges, such as Deployed 4 cartridges in 0:12. See Deployment columns.
A deployment opens its instance's Code Deployment tab: a row per cartridge with its state, progress, size and time, the status line and strip for the whole run, and a status bar item while it runs. Show in Console finds a cartridge's lines; Retry Failed and Skipped deploys only what did not make it

Bug fixes

  • Files the Salesforce firewall blocks: An upload the Salesforce firewall blocks, such as an ISML template that starts with <section, no longer fails. The file goes up zipped and is unzipped in its place, its row reads Uploaded zipped, and a notification says so. The workspace remembers the file, so its next uploads go zipped right away, on save, by hand and from agents. Stop Zipping in the notification, in the row menu or under Zipped Files on the Code Upload toolbar sends it as it is again. Every other file still goes as it is. See Files the firewall blocks.
Every upload to the instance lands in its Code Upload tab with its progress, size and time, and the status bar item says what goes up and how it went. Filter Uploads, Show Uploads of This File and Keep History narrow the list; Retry Failed Uploads and Clear History act on it. A file the Salesforce firewall blocks goes up zipped, and Zipped Files lists it
  • Switching branches outside VS Code: A checkout made in a terminal or another Git tool now reaches routes, pipelines, resource keys, custom APIs, ISML template and custom tag completion, XML problems, hook and job step gutter marks and B2C Doctor right away, also when a whole cartridge folder is deleted or comes back. A cartridge that disappears with the branch stays in your cartridge path and is linked again when it returns.

What's new in 1.0.0