madskristensen / WebEssentials2015

A Visual Studio extension for web developers
Other
300 stars 92 forks source link

Featrue request: Intellisense for custom tags #12

Closed am11 closed 9 years ago

am11 commented 9 years ago

Polymer, Knockout and many other HTML5 complaints front-end frameworks are engaged with this new thing called custom-tags (components-driven). Its basically about defining custom tags templates at client-end (as opposed to server-side "tag helpers", introduced in MVC6).

The HTML5 standard suggests that we need to have hyphenated name for our custom tags (say <pagination-tag data-id=".." per-page-"20" page-number="3"></pagination-tag> or <locale-transform culture="nl-NL">This text will be translated via an online translator tool.</locale-transform>).

Currently, there is no intellisense for custom tags and squiggly suggest that the tag is invalid. Although we can make intellisense custom-attribute-aware, but not the custom tag.

Please implement intellisense for client-side custom tags in HTML and Razor editors (and perhaps CSS editor too, for element selector? not sure), so to make it more familiar with HTML5 capabilities. I am not sure what would be the smartest course of action here: whether to have a white-list in WE's settings file or something more fancier like adding a template and calling it via <link rel="import" />, the polymer way?

Point to ponder: From intellisesne POV, would it be necessary to differentiate the client side custom tag with MVC6 TagHelper in Razor editor?


I don't know how this custom tags concept is so new to HTML5, it existed in HTML4 as well (via custom DTD I suppose?). I swear I saw custom tags back in 2004-05 in http://www.tek-tips.com/'s source.. But <link rel="import" /> thing is definitely quite a revolution. :)

am11 commented 9 years ago

@madskristensen, I know this should go to http://webessentials.uservoice.com/, but I am not sure if this is already possible, in development or under consideration.

madskristensen commented 9 years ago

This is on our backlog in the VS web team and we start working on it next week. I'm closing it here

am11 commented 9 years ago

Awesome! Thanks. :+1: