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
{{ message }}
This repository has been archived by the owner on Nov 15, 2019. It is now read-only.
...and then referring to the stored object instead of using __:
sportNames[chosenSport];
We regularly run into this issue and believe it is better solved inside the i18n plugin than in application code. It looks like an attempt at dynamic property names was being worked on in #42, but this turned into a 'plurals' feature in #58, which is not the problem we're trying to solve.
It may be possible for us to work on a PR for you if you are open to the feature idea. Thanks for your time 👍
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
My team would really benefit from dynamic properties, e.g.
Currently we have to work around the issue by manually maintaining a list of translations at compile time, e.g.
...and then referring to the stored object instead of using
__
:We regularly run into this issue and believe it is better solved inside the i18n plugin than in application code. It looks like an attempt at dynamic property names was being worked on in #42, but this turned into a 'plurals' feature in #58, which is not the problem we're trying to solve.
It may be possible for us to work on a PR for you if you are open to the feature idea. Thanks for your time 👍
The text was updated successfully, but these errors were encountered: