microsoft / microsoft/vscode-azureresourcegroups
Custom filtering for resource types
Open
Nobody has claimed this yet.
feature
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
@aweininger We discussed having some more filtering groups for resource types since we're starting to accrue a pretty large variety of extensions contributing.
Couple ideas:
- Hide some by default unless they have a resource of that type
- Have different filtering types, such as "Core" which would be our extensions, "Supported" which would be resources with corresponding extensions, and "All" which is showing every resource
- Maybe supporting a "Custom" filter that lets users filter similar to how it works for subscription. Have to consider how this will affect resource groupings.
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
No files, tests, or entry points are identified in the issue. Start by locating the existing resource-type and subscription filtering code, then clarify the intended Core, Supported, All, and Custom behavior and its effect on resource groupings before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100