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

Closed Unassigned: ObjectContent.Value to return T not object [1137]

$
0
0
Currently `ObjectContext<T>` returns `base.Value` which has type `object`.
Doesn't it make sense to introduce strongly-typed property to return `T` ( and change how is being kept internally)?
Comments: Hi, Thank you for clarifying the scenario. After further investigation we're not sure that this change can be done anyway due to a different change to ObjectContent. We made a change not too long ago where the "T" being stored inside the ObjectContent doesn't always exactly match what was initially set. This happens in OData query scenarios where sometimes the entity (e.g. "Customer") needs to be wrapped in a container type such as SingleResult<T>. As such, having a true strongly-typed "Value" property would not work all the time because the SingleResult<T> would not derive from "T". Thanks, Eilon

Viewing all articles
Browse latest Browse all 7215

Trending Articles



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