microsoft / microsoft/vscode-azureresourcegroups
Mark `resolveResource` as an activation event
Open
Nobody has claimed this yet.
🚧 engineering ⚙️
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
It's artificially inflating our user numbers since we're not excluding it as an activation event, but is happening pretty frequently because of the new view. I tried filtering this event out, and the numbers look normal.
- App Service
- Functions
- Static Web Apps
- Storage
- Virtual Machines
- Container Apps
- Databases
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
Start by locating the extension configuration or entry point that defines activation events and find where resolveResource is classified. Compare it with the existing Storage-related handling and verify that filtering resolveResource produces normal activation numbers, as described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100