Clément Habinshuti

### Describe the bug The `generate` command completes without generating code when you pass a V1 (or V2) schema. #### Version of the Project affected OData CLI 0.3.0 #### To...

OData CLI [documentation](https://learn.microsoft.com/en-us/odata/odatacli/getting-started) states that it supports generating Visual Basic client code  However it does not show you how to generate VB code. And when looking at the source...

E2E testing infrastructure

2

While we do have tests to verify that the generate code looks as expected and compiles without errors, we don't have tests to verify that the code we generate runs...

A customer wants to be able to configure the buffer size of `ODataUtf8JsonWriter`, e.g. increase the buffer size to reduce how frequent stream I/O is invoked. While `ODataUtf8JsonWriter` accepts a...

*Short summary (3-5 sentences) describing the issue.* `ODataUtf8JsonWriter` has a default internal buffer of 16k. When it gets full, it writes the data to the underlying output stream and then...

Dispose calls in constructors can lead to unwanted synchronous I/O.

1

We have cases in ODL code where we call `Stream.Dispose()` in the constructor, in a pattern like this: ```c# public ODataJsonLightOutputContext(...) { try { this.messageOutputStream = messageInfo.MessageStream; // ... }...

Provide async API for CsdlWriter

2

The `CsdlWriter` only exposes synchronous APIs for writing CSDL (`WriteCsdl` and `TryWriteCsdl`). This means that any async API that relies on `CsdlWriter` to serialize CSDLs (e.g. `ODataMessageWriter.WriteMetadataAsync`) will have to...