Edited Issue: WebAPI 5.1.0 crashes on IIS 7.0 with...
This is a breaking change in the 5.1.0 release. After deploying this update to our IIS 7.0 server with .NET 4.5.1 installed, each request handled by WebAPI seems to fail with the...
View ArticleCreated Unassigned: Attribute routing should support {action} in route for...
We should be allosed to use the {action} token when specifying routes so we do not have to repeat the method name everywhere...Current:[Route("SomeSuperAction/{id:int}")] public virtual ActionResult...
View ArticleCreated Unassigned: Support JsonProperty in SelectExpandWrapper [1676]
Modify the ToDictionary method of SelectExpandWrapper<T> to take into account JsonProperty when serializing the model.
View ArticleClosed Unassigned: Support case insensitive queries [1675]
Support case insensitive queries when parsing the OData query. This requires support for case insensitivity in the ODataUriParserComments: https://aspnetwebstack.codeplex.com/workitem/366
View ArticleCreated Unassigned: AllowedOrderByProperties should support paths [1677]
AllowedOrderByProperties doesn't make sense when the $orderby clause is something like Entity/NavigationProperty/ComplexType/Field which is a clause we support. Change the attribute name to allow...
View ArticleCreated Unassigned: We should check for navigability when parsing the OData...
We don’t to apply NotNavigable in the ODataQueryOptions validations (because setting NotNavigable will set the NotFilterable/Unsortable which will get validated just fine). That said we should apply it...
View ArticleEdited Unassigned: We should check for navigability when parsing the OData...
We don’t to apply NotNavigable in the ODataQueryOptions validations (because setting NotNavigable will set the NotFilterable/Unsortable which will get validated just fine). That said we should apply it...
View ArticleEdited Unassigned: AllowedOrderByProperties should support paths [1677]
AllowedOrderByProperties doesn't make sense when the $orderby clause is something like Entity/NavigationProperty/ComplexType/Field which is a clause we support. Change the attribute name to allow...
View ArticleEdited Unassigned: Support JsonProperty in SelectExpandWrapper [1676]
Modify the ToDictionary method of SelectExpandWrapper<T> to take into account JsonProperty when serializing the model.
View ArticleEdited Unassigned: Support JsonProperty in SelectExpandWrapper [1676]
Modify the ToDictionary method of SelectExpandWrapper<T> to take into account JsonProperty when serializing the model.
View ArticleEdited Unassigned: AllowedOrderByProperties should support paths [1677]
AllowedOrderByProperties doesn't make sense when the $orderby clause is something like Entity/NavigationProperty/ComplexType/Field which is a clause we support. Change the attribute name to allow...
View ArticleEdited Unassigned: We should check for navigability when parsing the OData...
We don’t to apply NotNavigable in the ODataQueryOptions validations (because setting NotNavigable will set the NotFilterable/Unsortable which will get validated just fine). That said we should apply it...
View ArticleEdited Unassigned: samples for $ref [1669]
A sample of getting entity reference link(s) with attribute route:```Example 24: URL addressing the references between Categories(1) and...
View ArticleEdited Issue: ODataUriUtils.ConvertFromUriLiteral in ODL beta1 doesn't...
ODataUriUtils.ConvertFromUriLiteral in ODL beta1 doesn't support enum.Fix the issue, once update to ODL later version.
View ArticleEdited Issue: IQueryable doesn't get serialized properly [1641]
When ODataqueryOptions get binded to the parameters and the query includes a select or an expand, the formatter should be able to serialize IQueryable<IEdmEntityObject>. CanWriteType does the...
View ArticleEdited Feature: Emit navigation properties with source multiplicity '*' if...
we emit properties with source multiplicity '0..1' by default if the target multiplicity is 1. users cannot configure the source end of the multiplicity. So, we should emit a better default which in...
View ArticleEdited Feature: Make KeyValueParser.ParseKeys support more format in OData...
Make the method ``` KeyValueParser.ParseKeys``` support more format in OData Uri BNF.For example, this parser won't handle the "JSON format for function parameters" (section 5 of...
View ArticleEdited Issue: SelectExpandQueryOption doesn't create the select expand clause...
``` public SelectExpandClause SelectExpandClause{ get{ if (_selectExpandClause == null){ ODataUriParser uriParser = new ODataUriParser(Context.Model, serviceRoot: null); _selectExpandClause =...
View ArticleEdited Feature: Provide ability to supply friendly Title for actions [520]
Currently we use the name of the Action even for the Title when advertising them. Provide ability to supply friendly Title for actions.Example(the title "Create Order" below):--------{"d":{...
View ArticleClosed Issue: FunctionImport doesn't apppear in the service document even if...
There are only entity sets in service document now: <?xml version="1.0" encoding="utf-8"?> <service xml:base="http://jinfutanwebapi2:9001/what" xmlns="http://www.w3.org/2007/app"...
View Article