Key Ignoring
Deprecated
These docs cover the legacy CLI (v0). The current CLI is v1. See the current CLI docs
Ignored keys are excluded from translation processing entirely. They do not appear in target files - the CLI skips them during content discovery and never sends them to the translation backend.
Configuration#
Add ignoredKeys to a bucket in i18n.json:
json
{
"buckets": {
"json": {
"include": ["locales/[locale].json"],
"ignoredKeys": ["internal/debug", "dev/testData"]
}
}
}How it works#
Given this source file:
json
{
"welcome": "Welcome to our platform",
"internal": {
"debug": "Debug mode enabled",
"testData": "Sample test content"
}
}With "ignoredKeys": ["internal/debug", "internal/testData"], the Spanish target file becomes:
json
{
"welcome": "Bienvenido a nuestra plataforma"
}The entire internal section is absent from the target file.
Key path notation#
Use forward slash (/) for nested keys and asterisk (*) for wildcards:
json
{ "ignoredKeys": ["internal/*", "dev/settings"] }Keys containing dots work naturally - dev/api.mock targets "api.mock" inside "dev".
Key Ignoring vs. Key Locking#
| Key Ignoring | Key Locking | |
|---|---|---|
| Appears in target files | No | Yes - with source value |
| Use case | Debug, test, internal content | Brand names, technical IDs |