We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No description provided.
The text was updated successfully, but these errors were encountered:
I remove this in https://github.com/buttondown/monorepo/commit/f39c9727f0de1cf9b08179a0b92a399a1e35ae3e#diff-e6ec570c49d15d43173d1f0b516ae521b1262c8eb68306ebb0ad40e37654557a because it was a surprisingly large performance bottleneck. I think we can bring it back by just exposing a new API route (not unlike needs_billing_information, which I deleted like a fool) and calling that in the generateCallouts flow.
needs_billing_information
generateCallouts
Sorry, something went wrong.
"Why is it a surprisingly large performance bottleneck" → because we have to count every unique subscriber for the account
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: