VSCode Extension - Long Resource Names + IntelliSense = Hard to navigate sometimes
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
Most of the IntelliSense suggestions that I've been using can usually be navigated with ease. For example `Microsoft.Web/` is relatively small and contains several child resources:

However with something as long as `Microsoft.OperationalInsights/workspaces` its hard to figure out what each entry actually is. Even the right portion of the popup is cut off.

## Possible Solution
### More descriptive context
Given the right portion of the popup renders `Provider / Resource / Child Resource / Child Resource @ Version` maybe we can parse it into smaller chunks:
> **Type**: `Microsoft.OperationalInsights/workspaces/linkedStorageAccounts`
> **Provider**: `Microsoft.OperationalInsights`
> **Resource**: `workspaces/linkedStorageAccounts`
or
> **Provider**: `Microsoft.OperationalInsights`
> **Type**: `workspaces/linkedStorageAccounts`
----
**UPDATE**
After researching I learned that VSCode does have the ability to resize these windows using the mouse. I still think that maybe rendering more information in the VSCode plugin could be beneficial?
Contributor guide
Research direction
Start by reproducing the long-resource-name IntelliSense popup in the VS Code extension, especially for Microsoft.OperationalInsights/workspaces/linkedStorageAccounts. Review the proposed provider and resource/type presentations, then define a concise rendering that keeps the full context visible and verify it against both short and long resource names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100