Chris Martinez

Currently - yes - this is expected, but only because I didn't realize that the OData packages were still targeting .NET Core 3.1 It's a goof on my part. Since...

_Preview 3_ is now available and there is a target for .NET Core 3.1. This issue did not auto-resolve because `main` isn't the default branch - yet. If everything works...

`6.0` has been officially released and .NET Core 3.1 is a supported TFM. It will remain that way until it is officially dropped by Microsoft support at the end of...

`GET` will never work. The `$batch` endpoint only accepts `POST`. The message body is always a MIME-encoded multipart document where each part is a nested HTTP message. The nested parts...

@knightian I'm not sure I fully follow the question. API Versioning doesn't specific care anything about OpenAPI (or Swagger). The API Explorer extensions will _bucketize_ all endpoints by API version...

I don't see how is related to batching (e.g. this issue) or OData; however, this happening for one or both of the following reasons: 1. You aren't using the required...

@joevanheerden were you ever able to get things working? @knightian even though your question was a segue, did you get things working as well?

@joevanheerden Good to know. OData is always seems to be a moving target. I've had reports of breaking changes or regressions between even patch versions. 😬 Glad you are unblocked....

@fannydengdeng This behavior is, unfortunately, _by design_. I tried to influence the OData 8.0 design early on to no avail. Its design assumes there can be only one `ODataOptions` and...

Just a quick update. It appears I _finally_ have something working. The native OData implementation isn't doing us any favors. I tried making things working over the existing implementation, but...