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

The global TranslationCleanupJob should be configurable per project #241

Open
cbaoth opened this issue Aug 14, 2015 · 0 comments
Open

The global TranslationCleanupJob should be configurable per project #241

cbaoth opened this issue Aug 14, 2015 · 0 comments

Comments

@cbaoth
Copy link

cbaoth commented Aug 14, 2015

The TranslationCleanupJob seems to remove obsolete keys + translations, those that are no longer available within the leading language file.

The problem here is, that this job performs the cleanup on all projects at once. There doesn't seem to be a way to configure this on a per-project basis. If you have many projects you want that each project admin can decide whether he wants to activate this cleanup mechanism for his project or not.

One simple solution could be, that projects get a "cleanup" flag so that the job only performs his cleanup action for those projects that have the "cleanup" flag set.

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

No branches or pull requests

1 participant