microsoft / microsoft/AzureStorageExplorer

Format JSON silently fails when content is not valid JSON

Open
#9,162 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:gear: adls gen2 :gear: blobs :gear: files :test_tube: testing
Dominant language
No language data
Stars
452
Forks
92
Avg merge
15h 20m
Merged PRs (30d)
3

Description

Storage Explorer Version

1.46.0

Regression From

Not a regression

Architecture

x64

Storage Explorer Build Number

20260821.10

Platform

All

OS Version

Windows 11 arm64/Windows 11 x64/MacOS Tahoe 26.6.2 /Linux Ubuntu 22.04

Bug Description

When previewing a JSON file in Storage Explorer, modifying the file content so that it is no longer valid JSON and then clicking Format JSON does not produce any visible response. The content is not formatted, and no error message, warning, or validation feedback is displayed.

Resource Types

Blobs, ADLS Gen2 blobs, File shares

Authentication Method

None

Connection Type

None

Steps to Reproduce
  1. Launch Storage Explorer.
  2. Expand one storage account -> Blob Containers.
  3. Create a blob container -> Upload one Json file.
  4. Modify the content so that it is no longer valid Json.
  5. Preview the JSON file -> Click Format JSON.
  6. Check the result.
Actual Experience

Clicking Format JSON has no visible effect.
Here is the gif:

Image
Expected Experience

It is better to validate the content before formatting.

Additional Context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the JSON preview and tracing the Format JSON action. The change is done when invalid JSON produces visible validation feedback instead of silently doing nothing, while valid JSON continues to format normally.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.