-
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-2877] Make OrganizationUser.AccessAll optional #4521
[AC-2877] Make OrganizationUser.AccessAll optional #4521
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4521 +/- ##
=======================================
Coverage 41.64% 41.64%
=======================================
Files 1271 1271
Lines 60187 60187
Branches 5527 5527
=======================================
Hits 25066 25066
Misses 33951 33951
Partials 1170 1170 ☔ View full report in Codecov by Sentry. |
New Issues
Fixed Issues
|
…-make-accessall-nullable
…-make-accessall-nullable
…anizationuser-sprocs-to-make-accessall-nullable
The |
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.
lgtm
🎟️ Tracking
https://bitwarden.atlassian.net/browse/AC-2877
📔 Objective
Step 1 of the EDD cycle in removing
OrganizationUser.AccessAll
from the database.These changes fall into 3 categories:
Views
This can be updated to remove AccessAll with no versioning, as Dapper mapping ignores missing and/or excess columns on read operations. It is already unused in the code.
Sprocs that do not use user-defined types
-./dbo/Stored Procedures/OrganizationUser_UpdateWithCollections.sql
These set a default value of
@AccessAll = 0
so that we can support 2 versions of the code (with and without the value).User-defined types
These are harder to update, you can't have optional columns on types, so we have to do it by versioning. Here we were already on version 2 so I've taken the opportunity to copy it back to a non-versioned name.
📸 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