#diegot_api

1 messages ¡ Page 1 of 1 (latest)

green fractalBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1256041946372116481

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

woeful prairie
#

Yeah I see what you ask. I can forward your feedback too but we haven't had a timeline to share, unfortunately

sleek canyon
#

yeah that can help, the problem I'm seeing now is that the deprecated tool has more features than the new version and even though there is a workaround with the meters (creating a new price + meter per subscription) it will be extremely messy to maintain (it doesn't scale)
To complement the original question, when will the support to the usage record be deprecated for good? The healthiest way, in this case, seems to be the usage of the legacy approach until the new one supports a distribution by subscriptions

woeful prairie
#

We don't have plan to deprecate it soon. Many of legacy API still exists today because a lot of users are already using it