aspnetcore/test/Microsoft.AspNet.Mvc.ModelB.../Binders
Doug Bunting 533474d07c Bind POCO model correctly; fallback to empty prefix despite exact name match
- #1865
- change `MutableObjectModelBinder` to ignore exact match in value providers
 - had an incorrect assumption: don't want exact model name to match since
   this binder supports only complex objects
 - also ignored `BinderModelName`, value provider filtering, et cetera
- reduces over-binding e.g. `[Required]` validation within missing properties

also add more tests of #2129 scenarios
2015-03-20 13:18:42 -07:00
..
ArrayModelBinderTest.cs
BinderTypeBasedModelBinderModelBinderTest.cs Removing ModelMetadataProvider.GetModelMetadataForParameters 2015-03-19 16:42:54 -07:00
BindingSourceModelBinderTest.cs Removing ModelMetadataProvider.GetModelMetadataForParameters 2015-03-19 16:42:54 -07:00
BindingSourceValueProviderTest.cs
ByteArrayModelBinderTests.cs
CancellationTokenModelBinderTests.cs
CollectionModelBinderTest.cs
ComplexModelDtoTest.cs
CompositeModelBinderTest.cs Bind POCO model correctly; fallback to empty prefix despite exact name match 2015-03-20 13:18:42 -07:00
DictionaryModelBinderTest.cs
FormCollectionModelBinderTest.cs
FormFileModelBinderTest.cs
HeaderModelBinderTests.cs Removing ModelMetadataProvider.GetModelMetadataForParameters 2015-03-19 16:42:54 -07:00
KeyValuePairModelBinderTest.cs `CompositeModelBinder.TryBind()` should return `null` more often 2015-03-20 13:18:13 -07:00
ModelBindingContextTest.cs Removing ModelMetadataProvider.GetModelMetadataForParameters 2015-03-19 16:42:54 -07:00
ModelBindingResultTest.cs
MutableObjectModelBinderTest.cs Bind POCO model correctly; fallback to empty prefix despite exact name match 2015-03-20 13:18:42 -07:00
TypeConverterModelBinderTest.cs