// Import Razor formatting log zips that the user has already downloaded from Azure DevOps feedback tickets or GitHub issues into FormattingLogTest, validate whether the captured problem still reproduces, and if needed drive a minimal repro plus fix workflow.
| name | formatting-log |
| description | Import Razor formatting log zips that the user has already downloaded from Azure DevOps feedback tickets or GitHub issues into FormattingLogTest, validate whether the captured problem still reproduces, and if needed drive a minimal repro plus fix workflow. |
Use this skill when:
Full_*_razor.zip or Range_*_razor.zip archive into the test suitesrc\Razor\src\Razor\test\Microsoft.VisualStudio.LanguageServices.Razor.UnitTests\TestFiles\FormattingLog\<TestName>\.[Fact] to src\Razor\src\Razor\test\Microsoft.VisualStudio.LanguageServices.Razor.UnitTests\Cohost\Formatting\FormattingLogTest.cs.DocumentFormattingTest, and then fix the product code.Full_*_razor.zip or Range_*_razor.zip attachment locally and give you the absolute zip path.Use the helper script in this skill:
.\.github\skills\formatting-log\scripts\Import-FormattingLog.ps1 `
-ZipPath C:\Users\dawengie\Downloads\Range_Index_razor.zip `
-WorkItemUrl https://dev.azure.com/devdiv/DevDiv/_workitems/edit/2878103 `
-TestName RanOutOfOriginalLines
-ZipPath must be a local file path. For Developer Community and Azure DevOps feedback tickets, ask the user to download the archive first instead of trying to fetch it yourself.-TestName defaults to a sanitized name derived from the zip filename. Override it when you want a shorter or more descriptive repro name.-Expectation Null only when the correct outcome is that all edits should be filtered out. Otherwise keep the default NotNull.src\Razor\src\Razor\test\Microsoft.VisualStudio.LanguageServices.Razor.UnitTests\Cohost\Formatting\FormattingLogTest.cs.dotnet test src\Razor\src\Razor\test\Microsoft.VisualStudio.LanguageServices.Razor.UnitTests\Microsoft.VisualStudio.LanguageServices.Razor.UnitTests.csproj --filter "FullyQualifiedName~FormattingLogTest.<TestName>"
Do not run dotnet test at the repo root.
FormattingLogTest.cs change by themselves.src\Razor\src\Razor\test\Microsoft.CodeAnalysis.Razor.CohostingShared.UnitTests\Formatting\DocumentFormattingTest.cs.FormattingLogTest plus the focused DocumentFormattingTest coverage.The formatting-log test, the minimal repro, and the fix should stay as separate commits during the investigation.
FormattingLogTest accepts both real range payloads and literal null Range.json files from full-document logs.[WorkItem("...")] with the originating Azure DevOps or GitHub URL on the imported test.Perform a branch snap (release branch cut) for dotnet repos like dotnet/roslyn. Use when: snapping a branch, cutting a release branch, creating a release branch, merging main into release, updating VS insertion config, updating darc subscriptions for a snap, moving milestones, or asked about snap workflow.
Install and validate a .NET SDK from an Azure DevOps internal build. Use this when asked to install, validate, or set up a .NET SDK from a dnceng/internal Azure DevOps build link or build ID.
Set up tracking for a new C# compiler feature: create test plan issue, feature label, update Language Feature Status page, and link related PRs. Use when: setting up a new language feature, creating a test plan, tracking a new csharplang proposal in roslyn, or asked to 'set up feature tracking'.
Run the razor-toolset-ci pipeline to validate the current branch against large third-party repositories (MudBlazor, OrchardCore, ASP.NET Core, etc.). Use when asked to run toolset tests, ecosystem tests, or third-party validation.
Create a merge branch from a chosen base, merge a chosen source/upstream branch into it, resolve common Roslyn conflicts (`.xlf`, `.resx`, compiler codegen), and summarize the resolutions.
Review code changes in dotnet/roslyn for correctness, performance, and consistency with project conventions. Use when reviewing PRs or code changes.