-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[PM-30613] Remove unused mjml-based-email-templates feature flag #6889
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
base: main
Are you sure you want to change the base?
Conversation
|
New Issues (2)Checkmarx found the following issues in this Pull Request
Fixed Issues (29)Great job! The following issues were fixed in this Pull Request
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6889 +/- ##
==========================================
- Coverage 60.01% 56.06% -3.96%
==========================================
Files 1971 1971
Lines 87090 87060 -30
Branches 7759 7758 -1
==========================================
- Hits 52266 48809 -3457
- Misses 32928 36443 +3515
+ Partials 1896 1808 -88 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@ike-kottlowski as discussed, I removed the old Handlebars templates and renamed the |
7012fb7
|
Had to resolve a merge conflict. |


🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-30613
📔 Objective
The
mjml-based-email-templatesflag was used to gate which method we used to send the Send OTP emails, as when we developed it we weren't sure whether MJML email services were going to be ready.Since they are ready for use, and the Send OTP email work is still in development to be consumed by the Tools team, adding this feature flag was not necessary and adds additional complexity and permutations to their testing. Rather than having Tools test with the flag off then the flag on, we'll just have it on to begin with and they'll use the new email as the basis for their 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