microsoft / microsoft/vscode-azureresourcegroups

The "global" location group doesn't display in FOCUSED RESOURCES view after focusing it

Open
#889 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: All
Build Version: v0.9.1
Regression: Not a Regression

Repro Steps:

  1. Make sure the resources Group by Location.
  2. Click "Focus Group" icon to focus the "global" location group.
  3. Check whether the "global" location group displays in the FOCUSED RESOURCES view.

Expect:
The "global" location group can automatically display in focused FOCUSED RESOURCES view after focusing it.

Actual:
The "global" location group doesn't display in FOCUSED RESOURCES view after focusing it.
image

More Info:

  1. There is a known bug about focus: https://github.com/microsoft/vscode-azureresourcegroups/issues/860
  2. For most of the location group, the resources can't be fully displayed in the FOCUSED RESOURCES view, as shown below:
    image

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 by grouping Azure resources by Location, focusing the "global" group with the Focus Group icon, and checking the FOCUSED RESOURCES view. Start by tracing the focus behavior from that view and verify that the global location group appears there after the change.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.