🐛 JSON file format with VSCode (save on format) do not match formatter

[fearless23]

Environment information

CLI:
  Version:                      12.1.3
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           windows

Environment:
  ROME_LOG_DIR:                 unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v18.16.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/9.5.1"

Rome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    true
  VCS disabled:                 true

Workspace:
  Open Documents:               0

Discovering running Rome servers...

Running Rome Server: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

i The client isn't connected to any server but rage discovered this running Rome server.

Server:
  Version:                      12.1.3
  Name:                         rome_lsp
  CPU Architecture:             x86_64
  OS:                           windows

Workspace:
  Open Documents:               0

Other Active Server Workspaces:

Workspace:
  Open Documents:               2
  Client Name:                  Visual Studio Code
  Client Version:               1.79.2

What happened?

1. Following is the .vscode/settings.json contents

{
  "[typescript]": {
    "editor.defaultFormatter": "rome.rome"
  },
  "[json]": {
    "editor.defaultFormatter": "rome.rome"
  },
  "editor.codeActionsOnSave": {
    "source.fixAll": true,
    "source.organizeImports.rome": true
  },
  "editor.formatOnSave": true,
  "editor.defaultFormatter": "rome.rome",
  "typescript.tsdk": "./node_modules/typescript/lib",
  "typescript.enablePromptUseWorkspaceTsdk": true
}

2. Following is the sample JSON file ( in this case tsconfig.json), let call this V1

{
	"compilerOptions": {
		"lib": ["ES2023"],
		"baseUrl": ".",
		"target": "ES2022",
		... other properties
	}
}

On Pressing Ctrl+S after editing this file, it is converted to following and , let call this V2

{
	"compilerOptions": {
		"lib": [
			"ES2023"
		],
		"baseUrl": ".",
		"target": "ES2022",
		... other properties
	}
}

Whereas, running rome format . --write, convert it back to V1. Thus, rome ci will fail if using V2.

Expected result

Expected to have same behavior from Rome CLI and Rome VSCode (Feature / format on save) extension, regarding JSON file formatting.

Code of Conduct

• I agree to follow Rome's Code of Conduct

[ematipico]

The rage command shows that you're not using the VSCode extension. Do you know which version of the extension you have installed?

[fearless23]

@ematipico updated the rome rage output, earlier it was truncated