-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
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
Improve Billing Breakdown section #20498
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
6 Ignored Deployments
|
Updates to Preview Branch (chore/improve-upcoming-invoice-view) ↗︎
Tasks are run on every commit but only new migration files are pushed.
Connecting to this Preview Branch
Branching Preview Branches by Supabase. |
942d21b
to
844f57d
Compare
75ddcf9
to
5429466
Compare
...udio/components/interfaces/Organization/BillingSettings/BillingBreakdown/UpcomingInvoice.tsx
Outdated
Show resolved
Hide resolved
...udio/components/interfaces/Organization/BillingSettings/BillingBreakdown/UpcomingInvoice.tsx
Outdated
Show resolved
Hide resolved
...udio/components/interfaces/Organization/BillingSettings/BillingBreakdown/UpcomingInvoice.tsx
Outdated
Show resolved
Hide resolved
...udio/components/interfaces/Organization/BillingSettings/BillingBreakdown/UpcomingInvoice.tsx
Show resolved
Hide resolved
...udio/components/interfaces/Organization/BillingSettings/BillingBreakdown/UpcomingInvoice.tsx
Outdated
Show resolved
Hide resolved
...udio/components/interfaces/Organization/BillingSettings/BillingBreakdown/UpcomingInvoice.tsx
Outdated
Show resolved
Hide resolved
...udio/components/interfaces/Organization/BillingSettings/BillingBreakdown/UpcomingInvoice.tsx
Outdated
Show resolved
Hide resolved
...udio/components/interfaces/Organization/BillingSettings/BillingBreakdown/UpcomingInvoice.tsx
Outdated
Show resolved
Hide resolved
Co-authored-by: Kevin Grüneberg <k.grueneberg1994@gmail.com>
What kind of change does this PR introduce?
Improve Billing Breakdown section in Studio
What is the current behavior?
What is the new behavior?
Additional info
There's still an issue with the calculation of the Projected Costs. Will be tackled with a different PR.