Exclude files for translation:delete-obsolete command

[DidierLmn]

I use this bundle to expose certain translations to the client side.

Since these translations are only used in JavaScript files, they are marked as obsolete. Is there an option to exclude the translation file(s) where the JS translations are located (for example js.en.xlf) when executing translation:delete-obsolete command?

[Nyholm]

Are your JS translations in a different domain?
If so, could you use the config option blacklist_domain to exclude that domain from the bundles config? Then the bundle will not touch those translations.

If you still need say, the webUI, then you should create a separate configuration.

translation: 
  configs: 
      default: 
          blacklist_domain: "javascript"
          # stuff
       js: 
          # other stuff

Im not sure something this will work. Could you give it a try and come back with your solution. I'll be happy to put it in the docs.

[DidierLmn]

Thanks for the suggestion, I was unaware of the blacklist_domain option.

I've tried it, but it doesn't seem to be able to work unfortunately. I've used this as a config in packages/php_translation.yaml:

translation:
    locales: '%locales%'
    configs:
        default:
            blacklist_domain: "javascript"
            dirs: ["%kernel.project_dir%/templates", "%kernel.project_dir%/src"]
            output_dir: "%kernel.project_dir%/translations"
            excluded_names: ["*TestCase.php", "*Test.php"]
            excluded_dirs: [cache, data, logs]

As you can see I've blacklisted the javascript domain, however it still shows up in the webUI

I've tried using blacklist_domains: ["javascript"] instead, but that doesn't seem to work either. I've cleared the Symfony and browser cache multiple times and restarted my server.

I'm not getting any errors or anything. Is it possible there's a bug in with the blacklist_domain option? Or is there anywhere else I can check or something I could've done wrong?
Thanks

[Nyholm]

I see that we do not respect the blacklist in all scenarios. I've added #220 to fix this issue.