[JN-1617] Allow cloning default email template when language doesn't exist yet #1465
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
connorlbark
requested changes
Feb 7, 2025
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DESCRIPTION (include screenshots, and mobile screenshots for participant UX)
Needed for A-T. Previously this functionality did not exist - if you tried to edit an email template in a language and that localized template did not exist yet, you couldn't do anything. Now you can clone the default language template.
Same UX as website content.
TO TEST: (simple manual steps for confirming core behavior -- used for pre-release checks)
Add a brand new language to Juniper Heart Demo: https://localhost:3000/demo/studies/heartdemo/env/sandbox/settings/languages
Confirm you can edit an email template in that new language by first cloning from default