Opt out translation

[MohamedMouloudj]

Problem

Currently, in order to opt out translation of some components I have to enable useDirective and add use i18n at the top of files I want to translate.
This is quite the opposite of the normal flow. Marking every file I want to translate consumes a lot of time, and even prone to being forgotten, causing extra commits and workflow computation.

Solution

Invert the operation.
Instead of marking the files that we want to translate with use i18n, we mark the ones we want to translate.

Visuals

Workarounds

No response

[The-Best-Codes]

I think the best approach here would be to keep the opt-in option, but make a new opt-out option in the config.

[gmpaliwal07]

Hey @vrcprl @maxprilutskiy ,

I was able to reproduce the issue and have implemented a fix in my local branch.

Here's what I did:
Added useDirective: "opt-out" as a new config option alongside the existing true/false
Added support for a "skip i18n" file directive to opt individual files out of translation
Updated types, logic, and tests - all 230 tests passing
Verified with a screen recording showing before/after behavior on the Next.js demo

How it works:
useDirective: false - all files translated, existing default, unchanged
useDirective: true - only files with "use i18n" are translated, existing opt-in, unchanged
useDirective: "opt-out" - all files translated except those with "skip i18n", new behavior

Before:
https://github.com/user-attachments/assets/053c92da-cd8a-46a3-8400-9e065c7cc400

After:
https://github.com/user-attachments/assets/b9c85fab-c274-4e21-a0be-1ed68ddf6807

In the after video, "skip i18n" is applied to the subtitle component. it stays in English while the action buttons translate correctly.

Could you assign this issue/feature to me? Happy to open a PR once assigned.

[gmpaliwal07]

@maxprilutskiy @vrcprl any updates on this ?