Interesting! Is there an escape hatch to drop down to raw Stripe primitives if someone needs a feature you haven’t modeled yet?
This feels like something many teams eventually build internally — curious how you’re thinking about long-term API surface + compatibility with new Stripe features.
Hey everyone, we were doing some repo admin and briefly changed the visibility of the repo from public -> private and back to public, then discovered in horror that we lost ALL the github stars and forks! Googling suggests that others have ran into this issue too and github is not able to restore it (see https://www.qovery.com/blog/we-lost-3800-stars-on-github-in-...).
PSA: Never change a public repo to private, not even for a moment, because doing so means you will irreversibly lose ALL your github stars and forks, there is no going back! :(
if it's postgres, then 5 mins as shown in the video :) Otherwise what data warehouse are you thinking of and what's the use case behind it?
Can you clarify what you mean by "not out of box" API? We haven't built an integration with Argyle yet but once we do it would be the same experience as Plaid