#jrfr-dotnet-customersession
1 messages ยท Page 1 of 1 (latest)
For some additional context I was looking at the releases here https://github.com/stripe/stripe-dotnet/releases
jrfr-dotnet-customersession
Hey @lusty bone ! The CustomerSessions API is in private beta (secret) so it's not in the official trunk
We do have a beta SDK pipeline, see https://github.com/stripe/stripe-dotnet#beta-sdks
oh i see I wasnt sure how to access that beta one I'll give that a shot! thanks
random question do you know how long an item in beta typically takes to make it to the official sdk?
depends on the beta. Some have been in beta for years :p
We don't have any timeline for that API to go public for now as it's limited to one specific use-case (which I assume you're a part of)
ha ok understood, yeah its of particular interest to us ๐
now that we have a beta pipeline for SDKs it's a lot better honestly. Before all developers had to write their own HTTP requests which meant really low beta adoption
hha yeah I was mentally preparing for that to be my only option. I'll give this beta a shot, thanks for pointing me to the right details
I had one followup question:
The page you linked it has a beta version "41.22.0-beta.1 - 2023-06-22" that mentions CustomerSession objects but there is also a later beta version "41.25.0-beta.1 - 2023-07-13" but that one doesnt list customersession object amongst the changes
yeah that's normal it's an incremental changelog
would the more recent beta have customer session or should I use the specific beta that mentions it?
the more recent beta would have it, unless a version in the middle explicitly removed it (unlikely)
Good luck ๐
Flagging we (people on this Discord server) can't really help with betas (there are many and lots of specificities and secrets) so you'd work with your point of contact at Stripe that gave you access if you have follow up questions!
understood, thanks for assisting on utilizing betas properly
Of course! I'm pushing the team to document all those betas cleanly somewhere
having to parse changelogs on a separate branch is messy at best :p
hha well it is nice this is very transparent just was a bit confused on how to parse that main changelog