Add translatedFieldsByLocale
property
#38
Merged
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.
Trying to build a custom UI around translatable fields proved to be quite the challenge for me and my team. We want to have tabs, but it's near impossible to sort the
data
property of theTranslatable
class by locale. So in this PR, I've added atranslatedFieldsByLocale
property to simplify this process and offer more flexibility in terms of other UI solutions.Here's an example of how we've implemented this solution with tabs in a custom mail template create view:
The result looks something like this: