Azure Table Storage implementation of ISessionStore: first-party or community package?

[joshhanson314]

I added the ISessionStore abstraction in #4832 (issue #4565), shipped in 10.1. I have an Azure Table Storage implementation of it that's been running in production for a while, backing Blazor server<->WASM state flow through the StateController, and I'd like to contribute it back as the first concrete ISessionStore provider. Ideally as first-party rather than a community package, given the precedent for provider packages with third-party deps already in the repo (Csla.Channels.RabbitMq, Csla.Channels.Grpc, Csla.Data.SqlClient).

The question: would you want this as a first-party package in the repo (e.g. Csla.Blazor.State.AzureTableStorage), or would you rather it live as a community package that you link from the docs?

Happy to go whichever way you prefer. Just let me know and I'll open the PR (or publish and send a docs link).

[rockfordlhotka]

I think it is a fine idea to add it to the repo - it would be a new nuget package that people can opt into correct?

Does it have integration into the UseCsla config system so someone can easily add it in Program.cs?

[joshhanson314]

Yes and yes. An opt-in NuGet package and integration with UseCsla so it's a one-liner in Program.cs. I'll submit the PR. Thanks!