ASP.NET Core OData in WASM

[groogiam]

I'm working on running ASP.NET Core OData in was to create an offline server with the same API surface area as my online. I had this previously working in .NET 5 with older versions of this library. However since the release of .NET 5 there have been some refactors and updates that have Task.Wait namely in StreamWrapper. These types of calls break wasm as it is single threaded. I was wondering if there is any way to work around? So far this only seems like it affects the ability to read metadata but there may be other places.

P.S.
This is related to this issue OData/odata.net#2372. So far I have found ways to work around most of these waits by changing the injected services in this library. But the issue above I don't see any way to work around using the DI.

Thanks for your help.

[groogiam]

I found a way around this by replacing the metadata controller.