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
Provide a @i18next-parser-warning-ignore (or equivalent if you don't like that name ha ha!) comment tag that will silent a warning on a specific code line.
Motivation
For specific reasons, we may have sometime to use dynamic key and then say good bye to the automatic generation.
However, the only way to keep the parser working is to completely ignore any warning by setting failOnWarnings to false.
Deactivate this is not ideal because we are not able anymore to spot some not authorized variable key usage during merge requests review processing.
Using this tag will allow us to be more flexible without losing this security.
Example
constkey='foo';const{ t }=useTranslation();// @i18next-parser-warning-ignoret(key);
The text was updated successfully, but these errors were encountered:
As an another alternative, we may also provide a ignoreNamespaces option. Indeed, we dedicated our dynamic key usage on a specific catalog named validation (see here for the usage).
Ignoring the complete namespace may also fit our needs.
馃殌 Feature Proposal
Provide a
@i18next-parser-warning-ignore
(or equivalent if you don't like that name ha ha!) comment tag that will silent a warning on a specific code line.Motivation
For specific reasons, we may have sometime to use dynamic key and then say good bye to the automatic generation.
However, the only way to keep the parser working is to completely ignore any warning by setting
failOnWarnings
tofalse
.Deactivate this is not ideal because we are not able anymore to spot some not authorized variable key usage during merge requests review processing.
Using this tag will allow us to be more flexible without losing this security.
Example
The text was updated successfully, but these errors were encountered: