Are you using client-side or server-side editing?: Client-side (local filesystem copy to IRIS Instance)
- VS Code Version: 1.116.0
- Extension Version: 3.8.1
- OS: Windows
- Server
$ZVERSION: IRIS for Windows (x86-64) 2025.1.4 (Build 561U) Wed Apr 1 2026 11:21:14 EDT
Steps to Reproduce:
- Open a
.cls file containing a method with multiple parameters and a [ Private ] keyword (example below).
- Save the file (triggers auto-format).
- Observe the formatted output.
Source before save:
Method Test(a, b) [Private ]
{
set me = "a"
}
Result after save with v3.8.1:
Method Test(a, b) [Private ]
{
set me = "a"
}
Expected result (behavior confirmed working in v3.6.0):
Method Test(
a,
b) [ Private ]
{
set me = "a"
}
Relevant workspace settings:
"objectscript.multilineMethodArgs": true,
"[objectscript-class]": { "editor.defaultFormatter": "intersystems.language-server" },
"editor.formatOnSave": true,
"intersystems.language-server.formatting.system.case": "word",
"intersystems.language-server.formatting.system.length": "long"
Two regressions compared to v3.6.0:
- Multi-line method arguments are collapsed to a single line.
[ Private ] bracket spacing is incorrect — extra trailing spaces appear inside the brackets.
Note: keyword casing (e.g. method → Method) still works correctly in v3.8.1.
Workaround: Downgrading to extension v3.6.0 fully restores correct formatting behavior. Downgrading only the Language Server did not resolve the issue.
Are you using client-side or server-side editing?: Client-side (local filesystem copy to IRIS Instance)
$ZVERSION:IRIS for Windows (x86-64) 2025.1.4 (Build 561U) Wed Apr 1 2026 11:21:14 EDTSteps to Reproduce:
.clsfile containing a method with multiple parameters and a[ Private ]keyword (example below).Source before save:
Result after save with v3.8.1:
Expected result (behavior confirmed working in v3.6.0):
Relevant workspace settings:
Two regressions compared to v3.6.0:
[ Private ]bracket spacing is incorrect — extra trailing spaces appear inside the brackets.Note: keyword casing (e.g.
method→Method) still works correctly in v3.8.1.Workaround: Downgrading to extension v3.6.0 fully restores correct formatting behavior. Downgrading only the Language Server did not resolve the issue.