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
As mentioned in issue #2, a pretty common use case is an object property changing which should invalidate existing translations. This is currently not possible through the API, as all methods for removing translations require a specific language argument.
Possible solutions:
allow a * argument instead of language identifier
add an invalidateTranslations() method, which has a similar signature to removeTranslations() but without the language parameter
The text was updated successfully, but these errors were encountered:
I am in a short trip till the 23rd, so I'll be able to give the full attention to both of the issues you've raised only afterwards.
For now I'll just say that #3 does look like something the API should have, and will have. #2 seems like a too specific problem that might be hard to generalize, I'm looking forward to see what ideas you'll come up with regarding its implementation in the API.
I like your * approach, if you'll implement it I'll pull it to the tree.
My time resources for open source development are pretty low now, so I won't be able to help with development, but if you need guidance to the code you can contact me directly on Skype: daniel.razoss .
As mentioned in issue #2, a pretty common use case is an object property changing which should invalidate existing translations. This is currently not possible through the API, as all methods for removing translations require a specific language argument.
Possible solutions:
*
argument instead of language identifierinvalidateTranslations()
method, which has a similar signature toremoveTranslations()
but without the language parameterThe text was updated successfully, but these errors were encountered: