Christof Sprenger

create better separation of concerns for unicode encoding and json formatting

5

The existing option "escapeNonAscii" seems to be a quick solution for some corner cases but blurs the difference between encoding unicode text into UTF-8 and formatting JSON content. The JSON...

Improve coverage of static properties for standard Annotation terms

4

The comment in https://github.com/OData/odata.net/pull/2036#issuecomment-882624198 it was mentioned that the code in src/Microsoft.OData.Edm/Vocabularies/CoreVocabularyConstants.cs and similar is time consuming to maintain in it's entirety. E.g.: ``` public static readonly IEdmTerm OptionalParameterTerm =...

strongly typed standard vocabulary APIs

4

Proposal to create a strongly typed standard vocabulary API as a new separate nuget package. today the standard vocabulary is exposed through types like `Microsoft.OData.Edm.Vocabularies.V1.CapabilitiesVocabularyModel` and `Microsoft.OData.Edm.Vocabularies.V1.CoreVocabularyModel`. But the coverage...

Refactor schema/model classes to improve construction and validation usability, and access performance

4

The model classes are well designed to separate the consumption (via the IEdmXYZ interfaces) and the classed to construct a model. But there are a few problems - we have...

EdmLocation has no usable properties.

4

IEdmLocatable is declared as returning an EdmLocation which is an abstract type without a property. which essentially requires to cast the returned value to something concrete. https://github.com/OData/odata.net/blob/4e263ca4b94d01f2d105d8282c62ec272cfcd1bb/src/Microsoft.OData.Edm/Schema/Interfaces/IEdmLocatable.cs https://github.com/OData/odata.net/blob/4e263ca4b94d01f2d105d8282c62ec272cfcd1bb/src/Microsoft.OData.Edm/EdmLocation.cs All reasonable...

Decouple ODataQueryOptions from ASP.NET/webAPI

2

*Short summary (3-5 sentences) describing the issue.* [ODataQueryOptions](https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnet.odata.query.odataqueryoptions?msclkid=044a791ec57c11ec862e99c31f654fc9&view=odata-aspnetcore-7.0 ) can not be easily constructed without an HTTP Context. But logically only a query string/query option and a schema is required....

Allow to modify ODataQueryOptions in controller action

2

There are scenarios where a service needs more control over the supplied query options before they are handed over to the QueryProvider (before they are "applied" to IQueryable : `queryOptions.ApplyTo(data)`)....

authorization middleware checking access to each segment

1

*Short summary (3-5 sentences) describing the issue.* [Documentation states](https://docs.microsoft.com/en-us/odata/webapiauth/how-permissions-are-applied#navigation-properties) : "If the endpoint accesses a navigation properties and nested paths in general, the authorization middleware will check whether the user...

Enum parameter binding can't be configured to be case in-sensitive.

1

The below mail has been sent to us to find out how enum parameter binding can be made case insensitive. From a quick investigation it seems that [EnumDeserializationHelpers](https://github.com/OData/WebApi/blob/0338075c9940fe29c6fd18cd3f9e0433fd82d745/src/Microsoft.AspNet.OData.Shared/Formatter/Deserialization/EnumDeserializationHelpers.cs#L48) Is calling...

wrong casing in serializing Scale facet in XML CSDL

1

the library writes for example `` but according to [4.01 sections 7.2.4 [Scale](https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_Scale)] and the [edm.xsd](https://raw.githubusercontent.com/oasis-tcs/odata-csdl-schemas/7249db75c4ee31ac959fafb99da6a79e2c6b9e02/schemas/edm.xsd) the XML string "Variable" should be "variable"