-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[PM-28265] storage reconciliation job #6615
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
Conversation
stage 3 stage 4 stage 5 final draft only allow in lower envs claude pr feedback tests claude feedback improvements
|
Great job! No new security vulnerabilities introduced in this pull request |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #6615 +/- ##
==========================================
+ Coverage 52.98% 53.10% +0.11%
==========================================
Files 1909 1902 -7
Lines 84828 84850 +22
Branches 7634 7631 -3
==========================================
+ Hits 44948 45057 +109
+ Misses 38127 38042 -85
+ Partials 1753 1751 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I'll analyze this and get back to you. |
amorask-bitwarden
left a comment
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.
Looking great - just had a couple questions.
| hasUpdates = true; | ||
| var currentQuantity = item.Quantity; | ||
|
|
||
| if (currentQuantity > 4) |
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.
Nice Work! Can we move the magic number 4 to a constant in the class? This would make it clearer what this value represents and easier to change if needed.


🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-28265
📔 Objective
Job to reconcile storage amounts and endpoints to trigger for testing.
⏰ 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