microsoft / microsoft/vscode-azureresourcegroups

The error disappears from the "Problems" windows and the opened .jsonc file after clicking on the "Output" window

Open
#101 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

AT-CTI
Dominant language
TypeScript
Stars
78
Forks
55
Avg merge
16h 49m
Merged PRs (30d)
139

Description

OS: Win 10
Build Version: 20210902.1
Regression: Not a regression

Repro Steps:

  1. Create one resource group -> Right click it and select "Edit Tags..." -> There is an error in the "Problems" windows and the opened .jsonc file.
  2. Click on the "Output" window.
  3. Check whether the error still exists in the "Problems" windows and the opened .jsonc file.

Expect:
The error still exists in the "Problems" windows and the opened .jsonc file

Actual:
The error disappears from the "Problems" windows and the opened .jsonc file.
resource

More Info:

  1. This issue does not reproduce when clicking on other windows, such as Terminal/Debug Console.
  2. This issue does not reproduce if the cursor focus on the opened .jsonc file again.
  3. This issue also reproduces on the previous released resource group extension.

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

Reproduce the issue using the resource group's "Edit Tags..." action with an opened .jsonc file, then compare the Problems and Output windows after changing focus. Trace the path that reports the error and observe what changes when the Output window is selected. Done means the error remains visible in both the Problems window and the opened .jsonc file.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, typescript, vscode
Domain
cloud, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.