[PM-37237] Move OrganizationsNew into ProfileResponseModel#7627
Conversation
Bitwarden Claude Code ReviewOverall Assessment: APPROVE This PR colocates Code Review DetailsNo findings. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7627 +/- ##
=======================================
Coverage 59.98% 59.98%
=======================================
Files 2133 2133
Lines 93725 93731 +6
Branches 8310 8311 +1
=======================================
+ Hits 56217 56226 +9
+ Misses 35528 35527 -1
+ Partials 1980 1978 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
JaredSnider-Bitwarden
left a comment
There was a problem hiding this comment.
Auth file changes LGTM! (there are merge conflicts on the PR though)
…ve-organizationsnew-into-profileresponse-model
|



🎟️ Tracking
PM-37237
📔 Objective
OrganizationsNewis the feature-flagged counterpart toProfileResponseModel.Organizations— both expose the user's organizations, the only difference being scope (Confirmed-only vs. Confirmed+Accepted). The current placement is awkward:OrganizationsNewlives onSyncResponseModelwhileOrganizationslives on the nestedProfileResponseModel, even though they are logically siblings.This PR colocates them by moving
OrganizationsNewontoProfileResponseModelnext toOrganizations. The data now flows through the profile object, andGET /accounts/profilealso returns it when the feature flag is enabled.This feature is still behind the
pm-34145-policies-in-accepted-stateflag and has not been released, so no backwards-compatibility is needed for clients.