Postman in VSCode doesn't format JSON correctly.

[RichardYusteDAW]

Is there an existing issue for this?

• I have searched the tracker for existing similar issues and I know that duplicates will be closed

Describe the Issue

I press the pretty option, but it doesn't format the line breaks correctly.

VSCode 1.95

Steps To Reproduce

1. press the pretty option

Screenshots or Videos

Operating System

Windows

Postman Version

1.3

Postman Platform

Other

User Account Type

Signed In User

Additional Context?

No response

[chemargar]

Richard, Do you have a temporal solution to this issue? I tried to change to a lower version of this extension but It doesn't work

[sarah-gelt]

+1 same issue here

VSCode details

Version: 1.95.0 (Universal)
Commit: 912bb683695358a54ae0c670461738984cbb5b95
Date: 2024-10-28T20:16:24.561Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 23.6.0

Postman plugin details

[eroSilva]

+1 same issue here

VSCode details

Version: 1.95.0 (Universal)
Commit: 912bb683695358a54ae0c670461738984cbb5b95
Date: 2024-10-28T20:16:24.561Z (2 days ago)
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 23.6.0

Postman extension version:
v1.3.0

[bordom]

+1 same issue here

Postman extension version:
v1.3.0

Running on macOS 14.7
with VSCode:

Version: 1.95.1
Commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
Date: 2024-10-31T05:14:54.222Z (1 day ago)
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 23.6.0

Also it might be worth mentioning that subsequent REST calls do not update the response in the "Pretty" view.
Only the "Raw" view is updated with the new response data.

[kakhagh]

same here

Version: 1.95.1
Commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
Date: 2024-10-31T05:14:54.222Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Linux x64 5.15.0-124-generic

however response from https://postman-echo.com/get?a=1&b=2 is formatted....

[duwejeferson]

Same here, Win 11 with WSL

Version: 1.95.1 (system setup)
Commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
Date: 2024-10-31T05:14:54.222Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631

[Dev-wonderful]

The temporary solution to this as highlighted in issue #13231 is to downgrade your VS Code version to 1.94.2, I haven't tried it but it works for the person

[DebbieB1]

Same. Seems like this is a recent issue. I thought I'd clicked a formatting button somewhere and messed things up.

Version: 1.95.1 (user setup)
Commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
Date: 2024-10-31T05:14:54.222Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045

[Salty-Sailor]

Due to VSCode being upgraded to version 1.95.1, my current workaround is to downgrade back to 1.94.2. Waiting for the official fix for this bug :)

[jaysonsosweet]

Annnnnnnnnnd.... same here.

[Bejjoeqq]

Same here :)

[divergent-synapse]

Oh, I thought I messed up a setting. Same issue here!

[DebbieB1]

Yeah, I wasted a good bit of time trying to figure out what I'd done wrong. Rolling back to 1.94.2 has me working for now.

Has anyone seen an ETA on this fix? I'm not sure if I want to turn off automatic updates for now or not so that I don't have to keep rolling back.

[juliboron]

+1

[pankajk07]

Hey folks, the issue seems to be in the underlying chrome of the latest version (1.95.1) of VSCode. We have raised the problem with the VSCode team in here and await their response.

As of now the only possible way to mitigate this is to downgrade your VS Code to an older version like v1.94.2.
We are actively tracking this issue and will update here if there is any development.

[ibrahim-sma]

Currently I am observing 2 issues in my POSTMAN in VS Code APP. Looks like both has open issues
Issue1: Response body pretty option is not working (Existing Issue #13230 )
Issue2: Glitch in Response received. Same as #13215
Postman always displays the older response, instead of current one.
Steps to Repro Issue2:

• Perform a new Request in VScode. Current State: Request1, Response1
• Perform another request in VSCode for same resource. Current State: Request2, Response1
• Now switch tabs in response body and check the response. Current State: Request2, Response2
  Description:
  When multiple requests on performed on the same resource, the response is always of the (n-1)th request.

[pankajk07]

Update: The VS Code team has recommended launching the VSCode instance by executing the following command.

code --disable-features=PlzDedicatedWorker

Currently, this is the mitigation step for this issue.
The VS Code team has added the issue to their November milestone and hopefully will be fixed in the next release

[ibrahim-sma]

Update: The VS Code team has recommended launching the VSCode instance by executing the following command.

code --disable-features=PlzDedicatedWorker

Currently, this is the mitigation step for this issue. The VS Code team has added the issue to their November milestone and hopefully will be fixed in the next release

Thanks @pankajk07 After using this workaround both the issues got resolved #13215 #13230

[parth-fundrev]

same issue here

[bibble235]

Thanks, suggested fix of running --disable-features=PlzDedicatedWorker worked for me

[alimr70]

Same issue. The suggested fix --disable-features=PlzDedicatedWorker didn't work on MacOs

[pankajk07]

@alimr70 Can please try the given command after quitting all of the instances of VS Code

[vuk-ivanovic-ananas]

Tnx this helped on mac after turning off vs code

[dzsoldado]

Still having the same issue, it only started after updating VS Code

Windows 11

Postman:

• Postman VS Code Extension Version: 1.4.1

VS Code:

• Version: 1.95.2 (user setup)
• Commit: e8653663e8840adaf45af01eab5c627a5af81807
• Date: 2024-11-07T11:07:22.054Z
• Electron: 32.2.1
• ElectronBuildId: 10427718
• Chromium: 128.0.6613.186
• Node.js: 20.18.0
• V8: 12.8.374.38-electron.0
• OS: Windows_NT x64 10.0.22631

[seanodaniels]

Same issue, and the --disable-features=PlzDedicatedWorker workaround worked for me. TY, and I am looking forward to a fix.

Version: 1.95.2 (user setup)
Commit: e8653663e8840adaf45af01eab5c627a5af81807
Date: 2024-11-07T11:07:22.054Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631