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
Right now, clean-ts command scans only .po files, which doesn't work well with other interchange file formats that are now supported (e.g. XLIFF) or any custom file naming conventions or future formats.
To make sure clean-ts logic is future-proof, we need to implement the following:
By default, assume that each directory with translation interchange files contains only files in one format; scan for all files in that folder, analyze their extensions and if extension is the same, delete all files with that extension. If there are multiple extensions, bail out (to prevent destructive command behavior if it accidentally configured to run against some random folder with important data).
Implement the --extenstions=xx,yy,zz (shorthand: --ext=xx,yy,zz) flag that will allow one to explicitly specify extensions of files to clean up.
Ignore (do not delete, and skip while traversing) directories and files that start with a dot (e.g. .cache or .gitignore). This will allow external synchronization plugins to store their synchronization cache/state right next to the synced data. It should be a responsibility of an individual TS sync plugin to clean up their cache if, for example, they see that there are no files to synchronize.
The text was updated successfully, but these errors were encountered:
Right now,
clean-ts
command scans only .po files, which doesn't work well with other interchange file formats that are now supported (e.g. XLIFF) or any custom file naming conventions or future formats.To make sure
clean-ts
logic is future-proof, we need to implement the following:--extenstions=xx,yy,zz
(shorthand:--ext=xx,yy,zz
) flag that will allow one to explicitly specify extensions of files to clean up..cache
or.gitignore
). This will allow external synchronization plugins to store their synchronization cache/state right next to the synced data. It should be a responsibility of an individual TS sync plugin to clean up their cache if, for example, they see that there are no files to synchronize.The text was updated successfully, but these errors were encountered: