This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Automatically convert ViewComponents to tag helpers #1051
Comments
NTaylorMullen
changed the title
Tag Helpers: Automatically convert ViewComponents to tag helpers
Automatically convert ViewComponents to tag helpers
Jan 23, 2015
My $100 for this feature. ;-) |
This was referenced Aug 18, 2016
cjqian
pushed a commit
to aspnet/Razor
that referenced
this issue
Aug 24, 2016
Added view component tag helper updates. aspnet/Mvc#1051
cjqian
pushed a commit
to cjqian/Razor
that referenced
this issue
Aug 25, 2016
cjqian
pushed a commit
to aspnet/Razor
that referenced
this issue
Aug 25, 2016
cjqian
pushed a commit
to cjqian/Mvc
that referenced
this issue
Aug 25, 2016
tag helper representations of view components. aspnet#1051
pranavkm
pushed a commit
to aspnet/Razor
that referenced
this issue
Aug 26, 2016
pranavkm
pushed a commit
to aspnet/Razor
that referenced
this issue
Aug 26, 2016
@NTaylorMullen: regarding what I meant about 'descendant tags'... I meant what if you nested view component tag helpers within each other, but it looks like that may be sorted out already by the use of self-closing tags. |
@tuespetre the default implementation of ViewComponentTagHelpers for its v1 representation will override its body content. Of course there's opportunity to expand on this later if it seems valuable. |
This was referenced Sep 1, 2016
tuespetre
pushed a commit
to tuespetre/Mvc
that referenced
this issue
Sep 8, 2016
This addresses aspnet#1051. There is one more pull request that needs to be completed/merged (for `CompositeTagHelperDescriptorResolver` and friends). After that, runtime should work!
cjqian
pushed a commit
that referenced
this issue
Sep 8, 2016
This addresses #1051. There is one more pull request that needs to be completed/merged (for `CompositeTagHelperDescriptorResolver` and friends). After that, runtime should work!
This was referenced Sep 20, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now we can invoke/render ViewComponents via
@Component.Invoke("MyViewComponentName", p1, p2....)
. We should consider making a "tag helper" alternative to rendering view components where you could do something like:<myViewComponentName />
This would involve automagically converting ViewComponent's into TagHelperDescriptor's. As for how they'd appear in html it's up for discussion.
The text was updated successfully, but these errors were encountered: