Closed warappa closed 3 years ago
@warappa thanks for contacting us.
@NTaylorMullen any thoughts?
@NTaylorMullen any thoughts?
So it'd be an interesting idea to decouple our language server from the actual file extensions. It'd be a two fold process where we'd need to make the compiler file path independent and then a second to change how our language server "detects" files.
One problem I don't envision being possible to easily overcome is that our language server has to watch the disk for specific file types (defined by file extension) in order to know when they get renamed, deleted, etc. This influences things like _ViewImports, possible Blazor components etc.
Thanks for contacting us. While this may be a great idea, it is not aligned with our long-term vision to make it part of the framework. For many other ideas which don't belong to the framework we encourage the community to build and ship on their own, contributing to the expanding .NET Ecosystem.
You can learn more about our triage process and how we handle issues by reading our Triage Process writeup.
Szenario
I want to use razor functionality with MJML templates in VS Code 1.51.1. (MJML is an responsive email framework to create an all-email-client-compliant html)
MJML-tooling switches file extensions while generating output, so I want to use the
.mjml
extension to describe the structure in MJML markup with Razor code interwoven, and then with MJML-tooling output a transformed regular.razor
file consumed later on by a templating service (RazorEngineCore).The Problem
I thought I just switch the language mode and everything is good. But:
SomeMailTemplate.razor
I get proper IntelliSense (with language mode beingaspnetcorerazor
).SomeMailTemplate.mjml
IntelliSense breaks, although I useChange Language Mode
to switch toaspnetcorerazor
.Expectation
A file-extension should not matter if I explicitly force the language mode to
aspnetcorerazor
.Reproduce
Add SomeMailTemplate.mjml file
aspnetcorerazor
Value
from@Model.Value
and trigger IntelliSense.razor
Further technical details
dotnet --info