-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[AC-3082] Split invoice history table into two tables for paid and open #11459
[AC-3082] Split invoice history table into two tables for paid and open #11459
Conversation
No New Or Fixed Issues Found |
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #11459 +/- ##
==========================================
- Coverage 33.19% 33.18% -0.02%
==========================================
Files 2772 2772
Lines 86068 86089 +21
Branches 16396 16400 +4
==========================================
- Hits 28573 28566 -7
- Misses 55229 55257 +28
Partials 2266 2266 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@@ -51,15 +58,20 @@ export class BillingHistoryViewComponent implements OnInit { | |||
: null, | |||
); | |||
|
|||
const accountInvoices = await invoicesPromise; | |||
const accountTransactions = await transactionsPromise; | |||
const openInvoices = await openInvoicesPromise; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⛏️ Can Promise.all
these if you want, but I'm not js-y enough to know it has any meaningful performance impact.
(cherry picked from commit 49b26db)
🎟️ Tracking
https://bitwarden.atlassian.net/browse/AC-3082
📔 Objective
Split the invoices table into two tables for two specific status: "open" and "unpaid."
📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes