aspnetcore/test/WebSites/FormatterWebSite
Doug Bunting c4fa402105 Add `ModelBindingResult.IsFatalError` and make body binding more consistent
- part I of II for #2445 (with a duplicate code PR to follow)
- needed for #2445 because new `ModelState` entries for values will make inconsisteny worse
- change `BodyModelBinder` to use same keys for all `ModelBindingResult`s and `ModelState` entries
 - return fatal error result if formatter adds an error to `ModelState`
 - update potential callers to avoid avoid ignoring `IsFatalError`
- fix test attempting to serialize all of `ModelState`
 - will be borked with additional `RawValue`s in state
- fix two other tests that serialized `ModelState` but checked only `IsValid`

nits:
- address minor inconsistencies in `ModelBindingContext`
- use `System.Reflection.Extensions` package a bit more, where it's already referenced
- remove some unused resources
2015-06-18 16:19:01 -07:00
..
Controllers
Filters
Models
wwwroot
FormatterWebSite.xproj
Startup.cs
StringInputFormatter.cs
ValidateBodyParameterAttribute.cs
project.json
readme.md

readme.md

FormatterWebSite

This web site illustrates how to input formatters operate on the request body. It also demonstrates how custom options can be set for model validation.