GiGStartr - Feature Request | Stripe Developers | Page 1

ebon jacinth Jul 25, 2022, 5:22 PM

#

Hello! Thank you for the feedback, I'll flag it internally. 🙂

#

Can you point me to the specific doc you're referring to? We do mark several docs pages as legacy now. Here's an example of one: https://stripe.com/docs/payments/charges-api

native wadi Jul 25, 2022, 5:29 PM

#

Well, spit'n'howdy, it's been started. I knew it hadn't been, and I see a lot of folk come here with Legacy questions, so I assumed it was still un-marked. Personally, I'd be a bit more obnoxious about it, but at least it's there now... BUt I'll note the API documentation doesn't seem to have that yet (and many, many people [for whatever reason]) only ever look at the APIs (e.g. https://stripe.com/docs/api/charges)

ebon jacinth Jul 25, 2022, 5:30 PM

#

Ah, that's a good point.

#

The Charges API itself isn't legacy; PaymentIntents generate Charges, for example, but specifically creating Charges is legacy and something we should consider marking as such in the API reference.

native wadi Jul 25, 2022, 5:32 PM

#

Coders tend to be a rather focused [blinkered?] lot, with a remarkable ability to ignore adjacent info, so I tend to be more... forceful... in such documentation

#GiGStartr - Feature Request