Edited 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 Issue: Consider more public surface area around...
Per HongMei: Consider extension methods to do things like get the list of all ODataMediaTypeFormatters, Get the OData model from the list of formatters. Consider exposing the supported payload kinds as...
View ArticleClosed Issue: Cache the compiled expression to improve performance [374]
[Performance] When the OData [Queryable] logic composes the query, it currently converts simple IEnumerable's to IQueryable using Enumerable.AsQueryable() when building the query expression. But...
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 ArticleSource code checked in, #76fde653c9eb
Fixing unit test failure in FacebookAuthorizeFilterTest.
View ArticleEdited Issue: EnableOData will convert HttpError to ODataError even it's not...
By EnableOData in an existing web api project, all the HttpError in the project will be converted to ODataError when client requests application/json or application/xml.<br /><br />The...
View ArticleCommented Issue: EnableOData will convert HttpError to ODataError even it's...
By EnableOData in an existing web api project, all the HttpError in the project will be converted to ODataError when client requests application/json or application/xml.<br /><br />The...
View ArticleEdited Issue: Queryable won't work for normal web api after adding odata...
The scenario is that after user added odata service to an existing web api application, the old api's queryable won't work as before.<br /><br />The reason is that we set the global edm...
View ArticleCommented Issue: Queryable won't work for normal web api after adding odata...
The scenario is that after user added odata service to an existing web api application, the old api's queryable won't work as before.<br /><br />The reason is that we set the global edm...
View Article