-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Razor Formatting no longer works? #218
Comments
I'm facing the exact same problem, but in my case I notice if I cut the line @model and try the formatting command, it works. Environment Information
|
@webreidi This issue is fixed pending release via dotnet/vscode-csharp#6236, however I don't have permissions to close this issue. Could you do it on my behalf? Thanks! |
@allisonchou thanks for the work tracking down this issue and resolving it 🙏! Which extension gets the fix and which version is it fixed in? Is this something I can test in my code today? |
@seangwright The fix should be in today's C# extension release (2.0.436). Could you try the new version and let us know if you still see the problem? Thanks! |
Everything looks good now! I can format Razor views and even my Thanks so much! |
Describe the Issue
Should Razor formatting be working? It definitely worked before I switched to the new DevKit.
Here's a video reproducing the issue
vscode-razor-formatting-not-working.webm
Here are my relevant VS Code workspace settings:
I hope I'm logging this issue in the correct repository, but as a related note, I now have a really difficult time understanding which parts of the tooling is controlled by each repository
Maybe it would be a good opportunity for a ASPNET Core Community standup episode for someone to explain all of these for the community. 🤔
Steps To Reproduce
Expected Behavior
The HTML, Razor and C# is all formatted correctly
Environment Information
ms-dotnettools.csharp
-2.0.248
ms-dotnettools.csdevkit
-0.2.99
1.79.2
8.0.0-preview.5.23280.8
global.json
7.0.305
The text was updated successfully, but these errors were encountered: