Nov 19, 2019 08:00 PM|Tyrven|LINK
I'm curious if you were ever able to solve this. If so, do you have additional tips to share on your implementation?
FWIW: I concur that a view component is an ideal way to approach this—and I'm using view components extensively for exactly this purpose in other contexts. My challenge is that in this case I need access to the
ModelExplorer.Metadata, which is populated in the ViewData with
asp-for. I'd like to replicate the functionality in my view components, so I can combine e.g. data access and business logic with contextual metadata about the property being bound to.