-
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-15506] Wire up vNextOrganizationService for libs/common and libs/angular #12683
base: ac/pm-15506-vNextOrganizationService
Are you sure you want to change the base?
[PM-15506] Wire up vNextOrganizationService for libs/common and libs/angular #12683
Conversation
…b.com:bitwarden/clients into ac/pm-15506-Wire-up-vNext-OrganizationService
New Issues
|
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## ac/pm-15506-vNextOrganizationService #12683 +/- ##
========================================================================
- Coverage 33.79% 33.71% -0.09%
========================================================================
Files 2911 2918 +7
Lines 90716 90997 +281
Branches 17154 17193 +39
========================================================================
+ Hits 30655 30676 +21
- Misses 57672 57928 +256
- Partials 2389 2393 +4 ☔ 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.
👍🏻 Tools code LGTM!
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-15506
📔 Objective
Partial implementation for wiring up vNextOrganizationService. This PR is organized by commits to make reviewing simpler for applicable teams. This PR will also include any services/components whose dependencies on the original OrganizationService would otherwise be broken by only updating the shared libs (this includes a few changes for all clients, mostly the CLI). The rest of the implementation will be spread out across their respective clients.
📸 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