Mvc: Make action descriptors descriptive

[javiercn]

We should do a pass through all the types that our users are likely to inspect when debugging ASP.NET MVC Core applications and implement debugger display on them so that its easier to see things like the route template on an attribute routed action or the HTTP method constraints on them.

[Eilon]

I'm ok with doing this, but only so long as we timebox it to some reasonable amount of time, e.g. 1 day to finish this item. We obviously can't go through _all_ the types in MVC/Razor/Routing and come up with plans for them, but if we can quickly come up with 10 - 20 types and implement debugger displays for them, let's go for it.

[m-henderson]

hi, could one of you give me a starting point for building out this feature? thanks (😀

[Eilon]

@javiercn / @mkArtakMSFT - do we have a good pointer on how to do this?

[Eilon]

These are some existing examples in this repo: https://github.com/aspnet/Mvc/search?utf8=%E2%9C%93&q=debuggerdisplay&type=

[khellang]

Also, take a look at @jaredpar's DebuggerDisplay attribute best practices (old, but still good) 😄

[javiercn]

The most interesting bit here is to decide where to put DebuggerDisplay on and what information to show. Our original idea was to keep this bug to track the progress we made and make the changes organically as part of other work items base on our own experience debugging.

That said, I can probably take a look at it sometime this week and provide some pointers. In general I would like to see things like the HTTP method constraints and the route (When using attribute routing).

It might be that some other things in the stack need to also have this done.

[mkArtakMSFT]

Hi. Thanks for contacting us.
We're closing this issue as there was no much community interest in this ask for quite a while now.