Quantcast
Channel: ASPNETWebStack Issue Tracker Rss Feed
Viewing all articles
Browse latest Browse all 7215

Edited Issue: Review the exception types thrown by the OData formatter consistent [727]

$
0
0
Probably doesn't meet the RTM bar.<br /><br />Youssef:<br /><br />About the InvalidOperation vs SerializationException, there are ~20 invalid operations thrown in the formatter namespace (more than the serialization exceptions). For consistency, we should either change them all to invalid operation or change them all to serialization exceptions.<br /><br />David:<br /><br />IMO, the case when IOE is correct is if it’s a matter of the object’s current state preventing the operation (rather than a parameter being invalid, in which case SE is better). I think there are some cases where the formatter requires state (like the request); in those cases, I think IOE makes sense. In all other cases, I’d go with SE.

Viewing all articles
Browse latest Browse all 7215

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>