- Updated attribute routing so it works now
- Created a Pages folder and PageController for serving pages, I don't
like views very much
- Worked around an EF issue
- Fixed ApiResult to use JsonResult.ExecuteResultAsync
- Made PagedList take the sort expression so it can be conditionally applied as calling Count on the query passed causes issues if it contains an OrderBy expression
- Made web server ports not conflict with non-SPA MusicStore
IActionConstraint follows a provider model similar to filters. The
attributes that go on actions/controllers can be simple metadata markers,
the 'real' constraint is provided by a set of configurable providers. In
general the simplest thing to do is to be both an
IActionConstraintMetadata and IActionConstraint, and then the default
provider will take care of you.
IActionConstraint now has stages based on the Order property. Each group
of constraints with the same Order will run together on the set of
actions. This process is repeated for each value of Order until we run out
of actions or run out of constraints.
The IActionConstraint interface is beefier than the equivalent in legacy
MVC. This is to support cooperative coding between sets of constraints
that know about each other. See the changes in the sample, which implement
webapi-style overloading.
- only affects an extreme corner case: user sets `metadata.EditFormatString` then reads
`metadata.DisplayFormatString`
- an extreme case because `EditFormatString` is normally set only when
`DisplayFormatString` is set and, if set, it's to the same value
- happened to see this while updating `CachedDataAnnotationsModelMetadata` for this PR
nit: an -> a in an adjacent XML comment in `CachedDataAnnotationsModelMetadata`
David Fowler
sornaks
Max Toro
YishaiGalatzer
DamianEdwards
N. Taylor Mullen
Brice Lambson
Peter Hsu
Pranav K
Eilon Lipton
jacalvar
Ryan Nowak
harshgMSFT
Doug Bunting
Chris Ross