microsoft / microsoft/vscode-azureresourcegroups
Comments in the tags.jsonc file will be lost after saving and reopening
Open
Nobody has claimed this yet.
AT-CTI
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
OS: All
Build Version: 20250220.1
Regression: Not a regression
Repro Steps:
- Create a resource group -> Right click it -> Edit Tags... -> Edit tags and add comments in the opened tags.jsonc file (such as the below screenshot) -> CTRL+S to save the change.
- Close the tags.jsonc file -> Right-click the above resource group and select "Edit Tags..." again.
- Check whether comments in the tag.jsonc file still exist or not.
Expect:
Comments in the tag.jsonc file still exist.
Actual:
Comments in the tag.jsonc file will be lost after saving and reopening.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Reproduce the issue through the resource group's “Edit Tags...” flow, add comments to the opened tags.jsonc file, save, close, and reopen it. Trace the tag editor's save and reload path; done means comments remain present after reopening, as described in the expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100