Clément Habinshuti
Clément Habinshuti
🚨 **IMPORTANT: Please do not create a Pull Request without creating an issue first.** *Any change needs to be discussed before proceeding. Failure to do so may result in the...
- Updates ODL version to 7.12.2 - Updates release version to 8.0.11
This issue was reported by an internal customer. They have separate classes to represent DB entities and API-visible entities: We are experiencing major performance regression in the Expand query when...
### Issues *This pull request fixes #2488 ### Description *Briefly describe the changes of this pull request.* ### Checklist (Uncheck if it is not completed) - [ ] *Test cases...
`ODataPath` has a constructor that takes `IEnumerable`, it copies these segments to its internal list of segments using the list constructor: `this.segments = new List(segments)`. `ODataPath` itself implements `IEnumerable`. So,...
*Summary describing the issue.* In a few cases, OData Client or ODL caches schema elements in static properties. This causes those schema elements to effectively remain alive for the entire...
Let's assume we have URL where the last segment is a stream property, and it has a $select query option: ``` /People(1)/StreamProp?$select=... ``` Then we parse this url with `parser.ParseUri()`...
This PR: https://github.com/OData/odata.net/pull/2431 provided support for injecting a custom `HttpClientHandler` which allowed us to address a number of long-standing issues, especially performance issues related to re-using http connections. However, injecting...
`HttpWebRequestMessage` is based on [`HttpWebRequest`](https://docs.microsoft.com/en-us/dotnet/api/system.net.httpwebrequest#remarks) which is no longer recommended for new development. ### Assemblies affected *Which assemblies and versions are known to be affected e.g. OData .Net lib 7.x*...
The current implementation of `ODataUtf8JsonWriter.WriteRawValue` manually writes to the stream. This is sort of a hack/workaround. `Utf8JsonWriter` provides a `WriteRawValue` method. This ideally what we should use, but it's only...