Using DisplayName directly can lead to unintended language names.

[riussi]

CodeStats.Client/CodeStats.Client/CommandFilter.cs

Line 41 in 1c38ebe

pulse.IncrementExperience(_textView.TextBuffer.ContentType.DisplayName);

Using _textView.TextBuffer.ContentType.DisplayName can lead to things showing up with things like "HTMLXProjection" for .cshtml-files.

[mastorm]

Hm. Thats ultra weird. One way would be asking @Nicd if he can remap them on the backend, but i somehow get the feeling that its something that they use for more than just cshtml, so i kinda need to find a workaround for that. Ill put some research in it. If someone knows what api it is, hit me up!

[Nicd]

It's not possible to alias "HTMLXProjection" to both "HTML" and "CSHTML" on the backend so need to find an API in the plugin that returns the correct language name.

[Nicd]

HTMLXProjection is now aliased to HTML.

[riussi]

Visual Studio code maps those as "Razor" which is the MS templating language.

[Nicd]

So which do you think it should be? I can remap it. What does VS show in its UI (language selector)?

…

On 9 Nov 2017 10.50, "Juha Ristolainen" ***@***.***> wrote: Visual Studio code maps those as "Razor" which is the MS templating language. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAQq8Tmaa-fGMqm_bHGPlBze4b5ucQgCks5s0rzegaJpZM4QXBqX> .

[mastorm]

You cant remap it to Razor. This has to be a plugin-side fix. The only thing you can do is keep it as HTML for now, because thats the "most consistent" solution. As long as its just Razor pages, I can check the file extension and send Razor if its cshtml - as an idea for a hotfix.