Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalidate all translations for a given key #3

Open
rijk opened this issue Sep 18, 2014 · 2 comments
Open

Invalidate all translations for a given key #3

rijk opened this issue Sep 18, 2014 · 2 comments

Comments

@rijk
Copy link
Contributor

rijk commented Sep 18, 2014

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
@theosp
Copy link
Collaborator

theosp commented Sep 18, 2014

Hi @rijk ,

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.

Thanks

@theosp
Copy link
Collaborator

theosp commented Sep 26, 2014

Hi @rijk ,

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 .

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants