#tidymince_docs
mighty riverBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1240311340669730876
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
lavish mist
Hello, thanks for the flag. To be clear does the code from the doc give you an error? If so can you send me the text of the error. We do try to keep the code in our docs up to date, so as far as I know the rest of our code should be accurate. But I can definitely flag that we need to review how we generate those Go code snippets
agile spade
It's a type error, so I can't compile following the example:
"cannot use stripe.String("now") (value of type *string) as *int64 value in struct literal"
lavish mist
Perfect, exactly what I was looking for.
agile spade
I'm testing the following which I guess is the updated version:
BillingCycleAnchorNow: stripe.Bool(true),
Replacing
BillingCycleAnchor: stripe.String("now"),
lavish mist
Thank you. I will raise that. I can see that there have been other errors reported with our Go snippets, but they are scattered and we address them when we get reports. So the Go language snippets should be up to date but mistakes do happen and we definitely appreciate the report when you run in to snippets that don't work.
Have you run in to any other issues with the code in our docs so far?
agile spade
Nope, this is the first one I see, all other docs are very nicely maintained, you're doing a great job 👌
lavish mist
Good to hear!