improve avm module completion readability with suffix labels and prefix descriptions#18958
Conversation
|
Test this change out locally with the following install scripts (Action run 23172691534) VSCode
Azure CLI
|
|
Hi @polatengin, thanks for this PR! Let's align on this internally first before proceeding. Thanks again! |
…paths, and descriptions
…ths, versions, and descriptions
…ving display names and simplifying paths
…dering module path and version information
…ving detail fields and enhancing section formatting
…consolidate module details
|
Just a heads-up, the AVM team has reviewed and approved these changes. This PR enhances the module completion tooltip to show rich documentation (display name, status, version, full path, description, and doc links) instead of relying on the narrow The changes are scoped to the completion provider and don't affect any core compilation or runtime behavior. All existing tests have been updated, and a new test has been added for the display-name tooltip integration. Would appreciate an expedited review when you get a chance. Thanks! 🙏 //cc: @matebarabas |
When authoring Bicep modules from the public registry (AVM), the completion dropdown is too narrow for the long module paths. Most AVM paths share long prefixes (e.g., avm/ptn/...) and differ only toward the end, making it hard to visually scan the list especially at higher editor zoom levels.
This PR enhances the module completion tooltip with rich, structured documentation instead of relying on the narrow
Detailfield:AvmModuleDisplayNameProviderfetches and caches AVM module display names and statuses from the Azure Verified Modules CSV indexes. The cache is loaded once on server startup, asynchronously.Tests added
Recording.2026-03-16.162230.mp4
Checklist
Microsoft Reviewers: Open in CodeFlow