Do you use client-side editing in VS Code? We want your feedback on the latest improvements!

Since our previous announcement, we have introduced several incremental improvements to the client‑side editing experience in VS Code. These updates focus on preserving developer‑authored formatting when synchronizing with the server.

What Changed

Client‑side *.cls files previously lost certain formatting details during compilation, including keyword casing (e.g., classmethod → ClassMethod), normalization of blank lines between class members, and removal of line breaks within parameter lists. The extension now separates formatting from the synchronization process so that user-defined formatting is retained.

In the typical client‑side workflow, only the Storage sections of classes are updated by the server. The recent changes ensure that synchronization updates only these sections, preventing unnecessary modifications to the rest of the file.

A new configuration option has been added: refreshClassesOnSync : boolean = false. By default, only the storage sections are refreshed after synchronization, preserving all other content, including formatting. Setting this value to true restores the previous behavior of refreshing the full class file.

Try and Provide Feedback

vscode-objectscript-3.6.1-storage.1.vsix.zip

1. Download the zipped VSIX file and unzip it.
2. Install the VSIX in VS Code using the standard extension installation instructions or by dragging the file into the Extensions view.
3. Follow your normal development workflow and evaluate the updated behavior. Please share your experience either here or in the associated GitHub pull request.