Fio 9618 #235
Merged
Fio 9618 #235
Conversation
This file contains hidden or 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
7 tasks
blakekrammes
force-pushed
the
fio-9618
branch
2 times, most recently
from
3371c01 to
1bfae0b
Compare
* FIO-9618 Update t() signature to pacify TS - TS was complaining about passing the rest args (...args) to Evaluator.interpolateString after the i18n class was moved to core (which has TS) - I think this is good anyhow since now we can reference the data param directly (data?.field) instead of doing args[0]?.field in the Evaluator's interpolateString method. * FIO-9618 add a couple premium translation strings for eamil rendering * FIO-9618: Add types to i18n shim
brendanbond
approved these changes
Apr 23, 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.
Link to Jira Ticket
https://formio.atlassian.net/browse/FIO-9618
Description
What changed?
Moved i18n shim from the renderer to here.
Why have you chosen this solution?
This allows for performing translations server-side, which is necessary for rendering emails without the renderer. Per Travis' suggestion.
Breaking Changes / Backwards Compatibility
n/a
Dependencies
Use this section to list any dependent changes/PRs in other Form.io modules
How has this PR been tested?
Manually, also via email rendering tests here.
Checklist: