Created Issue: $metadata requests should throw an exception when there is no...
Right now we just get a 406 with no error, because there are no formatters registered
View ArticleClosed Issue: OData: nullreference exception when return collection of...
public class Person { public int Id { get; set; } public string FirstName { get; set; } public string LastName { get; set; } } public class ShortPerson { public string FirstName { get; set; } public...
View ArticleClosed Issue: OData: Unknown $xxxx throws not supported with Queryable() [327]
Currently it doesn't support basics like $format and $inlinecount that all clients will pass. Most of the time we have no control over it. Unknown commands should not throw.Comments: Close the issue as...
View ArticleClosed Issue: Add parameter binder for supporting odata literal format. [325]
OData urls can contain edm primitives. The string representation of these primitives is different than what webapi (and .NET) uses causing model binding errors. For example, the url...
View ArticleEdited Issue: $metadata requests should throw an exception when there is no...
Right now we just get a 406 with no error, because there are no formatters registered
View ArticleCommented Issue: $metadata requests should throw an exception when there is...
Right now we just get a 406 with no error, because there are no formatters registeredComments: We should throw a better exception and move the clean inside the if block.
View ArticleCreated Issue: Considering support ModelState error in ODataError [565]
Discussed with Youssef that ODataError right now doesn't support custom error, so we will lose the modelstate's errors in odata error message.However, ModelState errors are very common in real...
View ArticleCreated Issue: Add containment support to the OData model builder [566]
We expose all the entity sets at the root level in the service document. we should support containment scenarios. As an example, entity set 'orders' is contained by the entity set 'customers'. One...
View ArticleCommented Issue: Add containment support to the OData model builder [566]
We expose all the entity sets at the root level in the service document. we should support containment scenarios. As an example, entity set 'orders' is contained by the entity set 'customers'. One...
View ArticleCreated Issue: Ajax.BeginForm() not sending submit button's name/value [567]
There are certain circumstances when using Ajax.BeginForm() and the underlying jquery.unobtrusive-ajax.js script that the name/value of the submit button is not posted to the server.See StackOverflow...
View ArticleCreated Issue: Asp.net MVC Paths Editor/Display Templates [568]
Please allow for using path names when using Editor or Display templates as you can currently do with views. Example: when using a View or Partial View can use the following path name...
View ArticleEdited Issue: Considering support ModelState error in ODataError [565]
Discussed with Youssef that ODataError right now doesn't support custom error, so we will lose the modelstate's errors in odata error message.However, ModelState errors are very common in real...
View ArticleCommented Issue: Considering support ModelState error in ODataError [565]
Discussed with Youssef that ODataError right now doesn't support custom error, so we will lose the modelstate's errors in odata error message.However, ModelState errors are very common in real...
View ArticleEdited Issue: Considering support ModelState error in ODataError [565]
Discussed with Youssef that ODataError right now doesn't support custom error, so we will lose the modelstate's errors in odata error message.However, ModelState errors are very common in real...
View ArticleEdited Issue: Add containment support to the OData model builder [566]
We expose all the entity sets at the root level in the service document. we should support containment scenarios. As an example, entity set 'orders' is contained by the entity set 'customers'. One...
View ArticleCommented Issue: Add containment support to the OData model builder [566]
We expose all the entity sets at the root level in the service document. we should support containment scenarios. As an example, entity set 'orders' is contained by the entity set 'customers'. One...
View ArticleEdited Issue: DataServiceVersion in $metadata should be 3.0 instead of 1.0 [496]
The attribute Indicates the version of the OData annotations used in the service metadata document. Client will use this value to check if it can read the document. Since we support inheritance and...
View ArticleCommented Issue: DataServiceVersion in $metadata should be 3.0 instead of 1.0...
The attribute Indicates the version of the OData annotations used in the service metadata document. Client will use this value to check if it can read the document. Since we support inheritance and...
View ArticleCommented Issue: Make primitive parameters non-nullable by default when they...
In the following action configuration, 'DateTime' parameter needs to be shown as Nullable="False" in the metadata document.ActionConfiguration:var product = products.EntityType;var extendSupportAction...
View ArticleEdited Issue: $metadata requests should throw an exception when there is no...
Right now we just get a 406 with no error, because there are no formatters registered
View Article