Format JSON silently fails when content is not valid JSON
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- desktop
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.
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
- Launch Storage Explorer.
- Expand one storage account -> Blob Containers.
- Create a blob container -> Upload one Json file.
- Modify the content so that it is no longer valid Json.
- Preview the JSON file -> Click Format JSON.
- Check the result.
Actual Experience
Clicking Format JSON has no visible effect.
Here is the gif:
Expected Experience
It is better to validate the content before formatting.
Additional Context
No response
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/AzureStorageExplorer
-
:beetle: regression :copilot: copilot :test_tube: testing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/AzureStorageExplorer#9191 · 1 comment ·
-
Difficulty 2/5 1-2 days Newbie friendliness 76/100
microsoft/AzureStorageExplorer#9186 ·
-
:globe_with_meridians: hard-coded string :globe_with_meridians: localization :test_tube: testing
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/AzureStorageExplorer#9152 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/AzureStorageExplorer#9207 ·
-
Sign-in errorOpen
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/AzureStorageExplorer#9206 · 1 comment ·
All issues in microsoft/AzureStorageExplorer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area:ai-suggestions bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
uttrflow/uttrflow-swift#4464 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
xingkongliang/skills-manager#516 ·
Maintainers usually reply within 5 days
-
bug chart-audit
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
lay295/TwitchDownloader#1675 ·