-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[PM-19180] Calculate sales tax correctly for sponsored plans #5611
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
|
Fixed Issues (4)Great job! The following issues were fixed in this Pull Request
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5611 +/- ##
==========================================
+ Coverage 46.71% 46.85% +0.13%
==========================================
Files 1615 1615
Lines 73563 73566 +3
Branches 6617 6618 +1
==========================================
+ Hits 34368 34466 +98
+ Misses 37753 37652 -101
- Partials 1442 1448 +6 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
cyprain-okeke
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.
Looks Good
|





🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-19180
📔 Objective
Sponsored organizations are created in two steps. The sponsorship is the second step where the familiy organization is converted into a family for enterprise organization which is free. Given how the code is otherwise written in the backend related to sponsorships, this proves rather challenging.
We also know we will still need to continue to charge sales tax correctly if the user buys additional storage. And we need to use the
PlanTypeto correctly determine whether the product is for personal use or business use to apply to correct automatic tax rules in Stripe.Related: bitwarden/clients#14129
📸 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