Skip to content
New issue

2025-03 March

Open
Overdue by 2 month(s)
•
Due by April 4, 2025
Last updated May 6, 2025
36% complete

List view

0 issues of 19 selected

  • Tooling needs focus rather than new features

    vscode
    Status: Open.
    #11414 In dotnet/razor;
    · afallingstone opened on Jan 24, 2025

  • [Cohosting] Decide what should happen if we can't get the document from the source generator

    needs design review
    New Feature Cohosting
    Status: Open.
    Task
    #11522 In dotnet/razor;
    · chsienki opened on Feb 20, 2025

  • Unskip VS Code completion tests

    flaky test
    Status: Open.
    #11502 In dotnet/razor;
    · davidwengier opened on Feb 16, 2025

  • Bug: Handle paths with <code>%20</code>

    vscode
    Status: Open.
    #10957 In dotnet/razor;
    · iyerusad opened on Oct 3, 2024

  • When typing "too fast", HTML element completions are omitted

    feature-completion
    Status: Open.
    #9725 In dotnet/razor;
    · Peter-Juhasz opened on Dec 17, 2023

  • HTML attribute completion broken if element has content

    feature-completion
    Status: Open.
    #10786 In dotnet/razor;
    · Peter-Juhasz opened on Aug 23, 2024

  • Error reporting is completely broken

    Status: Open.
    #11323 In dotnet/razor;
    · Peter-Juhasz opened on Dec 19, 2024

  • Add recurring integration test runs on different feature flag combinations.

    area-infrastructure
    Status: Open.
    #11284 In dotnet/razor;
    · phil-allen-msft opened on Dec 9, 2024

  • There should be one system for completion via LSP

    vscode
    Status: Open.
    #10367 In dotnet/razor;
    · phil-allen-msft opened on May 14, 2024

  • MVC Razor: Accepting an auto complete that requires new a new using generates garbage

    feature-completion
    vscode
    Status: Open.
    #10329 In dotnet/razor;
    · StringEpsilon opened on Apr 29, 2024

  • Typing <code>??&lt;space&gt;</code> in a razor method inserts from the completion list

    bugSomething isn't working
    feature-completion
    vscode
    Status: Open.
    #11381 In dotnet/razor;
    · ryzngard opened on Jan 11, 2025

  • Razor markup including parameters and on space word replacement.

    vscode
    Status: Open.
    #11290 In dotnet/razor;
    · afallingstone opened on Dec 11, 2024

  • New Formatting Engine Followup

    feature-formatting
    Status: Open.
    #11371 In dotnet/razor;
    · davidwengier opened on Jan 9, 2025

  • Combine semantic tokens precise range calls into one precise ranges call

    perf 📊
    Status: Open.
    #9273 In dotnet/razor;
    · phil-allen-msft opened on Sep 12, 2023

  • Change IRemoteServiceInvoker.TryInvokeAsync(...) to all callers to handle failures gracefully

    reliability 📊
    tech-debt
    Status: Open.
    Task
    #11431 In dotnet/razor;
    · DustinCampbell opened on Jan 31, 2025

  • blazor completion in vs removes the @ symbol for events

    feature-completion
    Status: Open.
    #11395 In dotnet/razor;
    · AdmiralSnyder opened on Jan 16, 2025

  • Breakpoints cannot be set in razor pages without code behind .cs files

    area-blazor
    Status: Open.
    #9968 In dotnet/razor;
    · AlexW68 opened on Feb 21, 2024

  • Close gaps in the complete set of available choices for Razor completion

    feature-completion
    Status: Open.
    #9807 In dotnet/razor;
    · phil-allen-msft opened on Jan 11, 2024

  • Navigating to Component within same RCL goes to razor__bg__virtual.cs

    Status: Open.
    #9361 In dotnet/razor;
    · garrettlondon1 opened on Oct 5, 2023
    •