Stephen Weatherford (MSFT) comments

Results 186 comments of


                                            Stephen Weatherford (MSFT)

If you click from an external source file to another tab and then back, the "Show..." code lens at the top of the file stops being clickable

I can still repro this (and so does @mumian) but can't seem to repro in git anymore so I'll have to investigate.

If you republish a module then force restore, the source displayed is the previous one, but the document links are from the new sources

It's likely this repros with the current released version, but I haven't tested it there, only main.

Restoring modules is slow and could be parallelized

@SimonWahlin I had a note that you were going to add some related bugs, but I can't remember what they were about...?

Breaking changes: Bump @microsoft/vscode-azext-utils from 2.1.0 to 2.3.1 in /src/vscode-bicep

@dependabot show ignore conditions

Breaking changes: Bump @microsoft/vscode-azext-utils from 2.1.0 to 2.3.1 in /src/vscode-bicep

@dependabot show vscode-azext-utils ignore conditions

Breaking changes: Bump @microsoft/vscode-azext-utils from 2.1.0 to 2.3.1 in /src/vscode-bicep

@dependabot show all ignore conditions

Breaking changes: Bump @microsoft/vscode-azext-utils from 2.1.0 to 2.3.1 in /src/vscode-bicep

@dependabot recreate

Bump MSTest.TestFramework from 3.2.0 to 3.2.2

@dependabot recreate

Document F12 for Bicep Registry

NOTES: THe first article ([Create private registry for Bicep module - Azure Resource Manager | Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/private-module-registry?tabs=azure-powershell#publish-files-to-registry)) goes into how the files look in the ACR. We should probably show...

Document F12 for Bicep Registry

Also, note that the ability to use --with-source is currently under an experimental flag (https://github.com/Azure/bicep/issues/13782), so not sure if you want to push the docs before we remove it (likely...