-
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
[PM-13645] fix seat count to include invited and accepted members #12848
[PM-13645] fix seat count to include invited and accepted members #12848
Conversation
New Issues (9)Checkmarx found the following issues in this Pull Request
|
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found.
Additional details and impacted files@@ Coverage Diff @@
## main #12848 +/- ##
==========================================
- Coverage 34.29% 34.29% -0.01%
==========================================
Files 2934 2934
Lines 90188 90189 +1
Branches 16939 16939
==========================================
Hits 30930 30930
- Misses 56794 56795 +1
Partials 2464 2464 ☔ 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.
Approved. One thing to think about. Do we need to always use all these params?
Good question, we should probably look into refactoring this into more focused components with params that make sense. I'll make a note of it and make a tech debt ticket to address it at some point. |
(cherry picked from commit 63a9c69)
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-13645
📔 Objective
This PR fixes the seat count to include members that are in invited and accepted statuses.
📸 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