Edited Feature: Add JSON Light support [483]
Need to set the ODataMessageWriterSetting.MetadataDocumentUri before calling ODataWriter
View ArticleEdited Issue: OData formatter handles content types incorrectly [588]
The OData media type formatter says it handles app/xml, app/atom+xml andapp/json;odata=verbose. However, it doesn't always support these content types. For example, for a feed, it only supports atom...
View ArticleEdited Feature: Attach request to the formatter for the OData code path [661]
We can attach the request to the formatter in the odata action selector.
View ArticleEdited Feature: $format is not supported [582]
ODATA services should support $format ($format=json and $format=atom) query string parameters.<br />As described here http://www.odata.org/documentation/uri-conventions#FormatSystemQueryOption .
View ArticleClosed Issue: application/json request returns odata=fullmetadata [642]
When asking for application/json on an odata json.light enabled service, the service returns application/json;odata=fullmetadata instead of application/json;odata=minimalmetadataComments: Fixed for RC
View ArticleCreated Issue: Convert MessageDetail in HttpError to ODataInnerError [703]
ODataError doesn’t support custom error, but it can have ODataInnerError, which can contain a nested InnerError, message, stack trace and type name.We should be able to use ODataInnerError.Message to...
View ArticleCreated Issue: ODataMediaTypeFormatter is case sensitive causing error during...
I receive the error below when accessing my People Feed at: http://localhost:51155/api/peopleIf I capitalize 'People' ie: http://localhost:51155/api/People, it works just fine.<m:error...
View ArticleCreated Issue: We should allow people setting the AllowedFunctionNames to...
[Queryable(AllowedFunctionNames=AllowedFunctionNames.AllFunctionNames)]IQueryable<Customer> Get(){..}This will throw exception saying that AllFunctionNames is not a valid enum value. Here is the...
View ArticleEdited Issue: We should allow people setting the AllowedFunctionNames to...
[Queryable(AllowedFunctionNames=AllowedFunctionNames.AllFunctionNames)]<br />IQueryable<Customer> Get()<br />{<br />..<br />}<br /><br />This will throw...
View ArticleCreated Issue: Navigation properties incorrect deserialization of key when...
using latest nightly of System.Web.Http.OData. using ODataConventionModelBuilder() and EnableOData() with Entity Framework.When using a string as the key, links are generated as...
View ArticleCommented Issue: Navigation properties incorrect deserialization of key when...
using latest nightly of System.Web.Http.OData. using ODataConventionModelBuilder() and EnableOData() with Entity Framework.<br /><br />When using a string as the key, links are generated as...
View ArticleEdited Issue: Navigation properties incorrect deserialization of key when...
using latest nightly of System.Web.Http.OData. using ODataConventionModelBuilder() and EnableOData() with Entity Framework.<br /><br />When using a string as the key, links are generated as...
View ArticleCreated Issue: Set MaxDataServiceVersion to 3.0 in model builder [707]
If we don't do that, client code won't work for V3 features like collection property.A workaround right now is to use following code:var model =...
View ArticleEdited Feature: OData does not support $inlinecount=allpages [330]
This is obviously very needed. See my comments about ODataResult on how this should be intelligently implemented without using things like ODataResult.
View ArticleCommented Feature: OData does not support $inlinecount=allpages [330]
This is obviously very needed. See my comments about ODataResult on how this should be intelligently implemented without using things like ODataResult.Comments: Fix added with this checkin:...
View ArticleEdited Issue: Set MaxDataServiceVersion to 3.0 in model builder [707]
If we don't do that, client code won't work for V3 features like collection property.<br /><br />A workaround right now is to use following code:<br />var model =...
View ArticleEdited Issue: Convert MessageDetail in HttpError to ODataInnerError [703]
ODataError doesn’t support custom error, but it can have ODataInnerError, which can contain a nested InnerError, message, stack trace and type name.<br /><br />We should be able to use...
View ArticleEdited Issue: Consider different signature for...
Per HongMei<br /><br />Some possibilities:<br />Return Collection<T> instead of IEnumerable<T><br />Move the method to ODataMediaTypeFormatter and call it something...
View ArticleEdited Issue: Consider different signature for...
Per HongMei<br /><br />Some possibilities:<br />Return Collection<T> instead of IEnumerable<T><br />Move the method to ODataMediaTypeFormatter and call it something...
View ArticleEdited Issue: Consider adding a type hierarchy under ODataMediaTypeFormatter...
Per HongMei: Consider classes like JsonODataMediaTypeFormatter, AtomODataMediaTypeFormatter, XmlODataMediaTypeFormatter, etc.
View Article