Implement IAlgodClient using dotnet SDK

[jasonboukheir]

One issue in the implementation is that IAlgodClient returns AlgoApiRequest<*>.Sent types for building out IProgress and CancellationToken parameters, while the dotnet SDK returns basic Task<*> types.

The AlgoApiRequest<*>.Sent needs a UnityWebRequest to build. Since we're already overriding the HttpMessageHandler to use UnityWebRequest, we can use the sent UnityWebRequest to recreate an AlgoApiRequest<*>.Sent and return that instead. Unfortunately, the only way to do this is to set a reference of the last sent UnityWebRequest.

If we want to allow multithreading, then this will require a lock statement on the overridden HttpMessageHandler.

Here's the plan:

1. Implement HttpMessageHandler using UnityWebRequest, and expose a LastSentRequest property that is set whenever SendAsync is called. Call this UnityHttpMessageHandler.
2. Construct the dotnet SDK API classes using UnityHttpMessageHandler.
3. When calling any of the dotnet SDK API endpoints, call lock(unityHttpMessageHandler) to prevent other threads from accessing it. The lock will release once the http message is sent and the LastSentRequest can be accessed.
4. Take the LastSentRequest and use it to construct the AlgoApiRequest<*>.Sent.

There is still the issue of serializing / deserializing data models using the dotnet sdk. The solution here could be to fallback on the dotnet sdk serializer if the type is not found in the algosdk formatters.

[github-actions]

🎉 This issue has been resolved in version 4.0.0-pre.1 🎉

The release is available on:

• npm package (@pre dist-tag)
• GitHub release

Your semantic-release bot 📦🚀