This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
ModelState error for FormatException should show DisplayName of the problematic property if available #3227
Comments
dougbu
added a commit
that referenced
this issue
Oct 22, 2015
…atException` and `OverflowException` - #3227 - much of change is to tests, creating and passing `ModelMetadata` - updated `InputFormatterContext` to make `ModelMetadata` available to `JsonInputFormatter` - walk `ModelMetadata` tree to get information about property with an issue - add missing `null` checks in `ModelStateDictionaryExtensions`
dougbu
added a commit
that referenced
this issue
Oct 22, 2015
…atException` and `OverflowException` - #3227 - much of change is to tests, creating and passing `ModelMetadata` - updated `InputFormatterContext` to make `ModelMetadata` available to `JsonInputFormatter` - walk `ModelMetadata` tree to get information about property with an issue - add missing `null` checks in `ModelStateDictionaryExtensions`
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
ModelStateDictionaryaddsResources.ModelError_InvalidValue_GenericMessageandResources.ModelError_InvalidValue_MessageWithModelValuemessages when aFormatExceptionoccurs. This message includes the full key (property / collection path) e.g. "model.Customer.Name". For consistency with MVC 5 and usability, should instead use theDisplayNameof the problematic property and fall back to the property name.The text was updated successfully, but these errors were encountered: