[PM-37953] Add OrganizationUserStatusType.Staged, Remove Ordinal Checks#7780
[PM-37953] Add OrganizationUserStatusType.Staged, Remove Ordinal Checks#7780sven-bitwarden wants to merge 7 commits into
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #7780 +/- ##
==========================================
+ Coverage 61.05% 65.51% +4.45%
==========================================
Files 2173 2173
Lines 96580 96598 +18
Branches 8691 8691
==========================================
+ Hits 58963 63282 +4319
+ Misses 35516 31126 -4390
- Partials 2101 2190 +89 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Bitwarden Claude Code ReviewOverall Assessment: APPROVE Reviewed the introduction of Code Review DetailsNo findings. The previously raised bot threads ( |
|
| Type = OrganizationUserType.User | ||
| }; | ||
|
|
||
| private static OrganizationUser GetStagedOrganizationUser(Organization organization, User user) => new() |
There was a problem hiding this comment.
maybe make this a public ext method on org user for this project? Since its in two different tests.
Can go alongside OrgTestHelpers.cs
jrmccannon
left a comment
There was a problem hiding this comment.
One tiny thing. I'm fine if you don't do it.



🎟️ Tracking
PM-37953
📔 Objective
Tip
A vast, vast majority of this PR consists of tests and migrations - each adjustment to actual business code is only a line or two.
Following the technical breakdown for settings applicable to provisioned-but-not-invited users, we are introducing a new
OrganizationUserStatusType. The largest challenge in doing so, is our internal inconsistencies with how we go about checking this value, causing any new addition to suddenly be included in a random assortment of queries.This PR makes all checks consistent - when evaluating this property, we should only be concerned about what we want included, not what we want excluded (or other nondeterministic-over-time checks).