You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which Transloco package(s) will this feature affect?
Transloco
Is your feature request related to a problem? Please describe
We have an array of strings that are random localized placeholders for an input box. In our program we add them as arrays and in our ui I can then easily create a random function that returns an random index to a translated string.
Describe the solution you'd like
When passing a string like SOME_FEATURE.PLACEHOLDER.0 it refers to the index in the JSON array at that JSON path.
Describe alternatives you've considered
We could also add a _ to all strings SOME_FEATURE.PLACEHOLDER_0 but I think this is a reasonable feature.
Additional context
No response
I would like to make a pull request for this feature
Yes 🚀
The text was updated successfully, but these errors were encountered:
Oh. Since you use flat with safe, it wont work actually with transloco. I tried it with a simple test, setting the value to false my test pass but others fail. So this is a heavy breaking change. Any suggestions?
Is there an existing issue for this?
Which Transloco package(s) will this feature affect?
Transloco
Is your feature request related to a problem? Please describe
We have an array of strings that are random localized placeholders for an input box. In our program we add them as arrays and in our ui I can then easily create a random function that returns an random index to a translated string.
Describe the solution you'd like
When passing a string like
SOME_FEATURE.PLACEHOLDER.0
it refers to the index in the JSON array at that JSON path.Describe alternatives you've considered
We could also add a
_
to all stringsSOME_FEATURE.PLACEHOLDER_0
but I think this is a reasonable feature.Additional context
No response
I would like to make a pull request for this feature
Yes 🚀
The text was updated successfully, but these errors were encountered: