You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when showing spending notifications to users we use the UsageService.ListUsage RPC and we sum up all the records. This is suboptimal, but more importantly it is the wrong data. Instead, we need to be looking at the current value of an Invoice (unpaid).
To that end, we want to add a new RPC to the BillingService. The RPC should be able to do the following:
Given a UserID, or TeamID, it find details about the latest invoice and retrieves the current value of that invoce (along with more info if needed)
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Currently, when showing spending notifications to users we use the
UsageService.ListUsage
RPC and we sum up all the records. This is suboptimal, but more importantly it is the wrong data. Instead, we need to be looking at the current value of an Invoice (unpaid).To that end, we want to add a new RPC to the
BillingService
. The RPC should be able to do the following:The text was updated successfully, but these errors were encountered: