- changed status to resolved
Update legacy 'controller-action' routing to attribute-based routing
Issue #911
resolved
First versions of web api controlled routing through the WebApiConfig.cs
in App_Start, and [ActionName()]
attributes.
This is clumsy, and using explicit routes as attributes is easier to understand.
e.g.
[ActionName('filter')]
gets replaced with
[Route("collection\filter"1)]
Ultimately most of the code in WebApiConfig can porobably og.
Similarly, Routeconfig.cs
defines the Mvc routing rules. These can also be eliminated by using mvc Attribute routes
this is a follow-on from #821
Comments (1)
-
reporter - Log in to comment
task(api): add standard GET endpoints for reading collections, with filter in the Uri
Resolves
#821#911→ <<cset 8c9a28710f2b>>