Yeah Auto CRUD was a gap that needed filling, but it wasn’t straight forward to determine what could & needed to be declaratively implemented in CRUD Services to avoid needing an implementation and why it required a lot of new declarative attributes with #Script integration to be able to cover a wide functional surface area that can be implemented via attributes.
The BlazorClient.cs API is a starting point to create an official public API with a known working configuration that we can later enhance as we know of more features Blazor supports without issues:
var client = BlazorClient.Create(baseUrl);
This API also lets you modify the MessageHandler all Blazor client instances are configured with:
BlazorClient.MessageHandler = new HttpClientHandler { ... };
It’s still unclear how much JSON Serialization implementation Blazor can support, historically crippled .NET Runtimes like Blazor have done poorly with reflection-heavy libraries like Serialization where it might end up the most supported way to invoke ServiceStack Services without issues would be to generate a protoc C# gRPC Client as the generated clients can be created without runtime reflection.