Deducing the view path from the model name?

[d3jv]

Hi,

Is it (or would it be) possible to be able to only provide a model and deduce the view path from that? I'm thinking something akin to doing return View() in ASP.NET Core MVC and the framework looking for the view based on the controller method name instead of a hardcoded path.

[soundaranbu]

Hi @d3jv, I assume this is to be used only in the controller action method? For any other workloads, it wouldn't work as it won't run in the context of a controller. To keep things consistent and simple to use, I would prefer not to introduce new APIs that would work only in specific type of applications.

[d3jv]

No, I meant like deducing the view path from the model or something along the lines. Such that the view paths don't have to be hardcoded strings. Can't think of a good way though to be honest.

[soundaranbu]

Ah yes I agree. The same problem exists in MVC as well. Using source generators could be an option where we would be able to generate the constants for the cshtml file paths like how aspire is able to generate the types for the projects. It can either be part of this library or a separate one. This could be a fun experiment to pursue.