> ## Documentation Index
> Fetch the complete documentation index at: https://glotctl.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# glot fix
> Auto-insert glot-message-keys comments for dynamic translation keys
The `fix` command automatically inserts `glot-message-keys` comments for dynamic translation keys that cannot be statically analyzed. This declares expected keys so that glot can track them properly.
## Usage
```bash npm theme={null}
npx glot fix [OPTIONS]
```
```bash pnpm theme={null}
pnpm exec glot fix [OPTIONS]
```
```bash yarn theme={null}
yarn glot fix [OPTIONS]
```
```bash bun theme={null}
bunx glot fix [OPTIONS]
```
## Options
Actually insert comments. Without this flag, glot runs in dry-run mode and
only shows what would be changed.
Override the source code root directory. Defaults to the value from configuration file.
Override the messages directory path. Defaults to the value from configuration file.
Override the primary locale. Defaults to the value from configuration file.
Enable verbose output for debugging.
## Why Use Fix?
When you use dynamic translation keys like ``t(`${prefix}.label`)``, glot cannot determine which keys are used at build time. This causes two problems:
1. **Dynamic key warnings** - The `check` command reports these as warnings
2. **Clean refuses to run** - The `clean` command won't run to prevent accidental key deletion
The solution is to add `glot-message-keys` comments that declare which keys are expected. The `fix` command automates this by:
1. Analyzing your template literal keys
2. Inferring appropriate glob patterns
3. Inserting the correct comment syntax (JSX or JS)
## What Gets Fixed
Keys using template literals with dynamic parts:
```tsx theme={null}
t(`${prefix}.submit`) // Fixed: pattern "Namespace.*.submit"
t(`error.${code}`) // Fixed: pattern "Namespace.error.*"
t(`items.${type}.label`) // Fixed: pattern "Namespace.items.*.label"
```
**Pure variable keys** cannot have patterns inferred:
```tsx theme={null}
t(keyName) // Cannot fix - no pattern can be inferred
t(getKey()) // Cannot fix - runtime value
```
For these, you must manually add `glot-message-keys` comments.
## Dry-Run Mode (Default)
Preview what comments would be inserted:
```bash npm theme={null}
npx glot fix
```
```bash pnpm theme={null}
pnpm exec glot fix
```
```bash yarn theme={null}
yarn glot fix
```
```bash bun theme={null}
bunx glot fix
```
Output:
```
--> ./src/components/Button.tsx:6:21
|
6 | return ;
| ^
+ {/* glot-message-keys "Common.*.submit" */}
Would insert 1 comment(s) in 1 file(s).
Run with --apply to insert these comments.
```
If there are unfixable variable keys, they are reported separately:
```
Cannot fix 1 dynamic key(s) (variable keys without pattern hints):
--> ./src/components/Dynamic.tsx:5:19
|
5 | return {t(keyName)};
| ^
= reason: variable key
```
## Apply Changes
Insert the declaration comments:
```bash npm theme={null}
npx glot fix --apply
```
```bash pnpm theme={null}
pnpm exec glot fix --apply
```
```bash yarn theme={null}
yarn glot fix --apply
```
```bash bun theme={null}
bunx glot fix --apply
```
Output:
```
--> ./src/components/Button.tsx:6:21
|
6 | return ;
| ^
+ {/* glot-message-keys "Common.*.submit" */}
Inserted 1 comment(s) in 1 file(s).
```
## Result
Before:
```tsx theme={null}
const t = useTranslations("Common");
export function Button({ prefix }: { prefix: string }) {
return ;
}
```
After:
```tsx theme={null}
const t = useTranslations("Common");
export function Button({ prefix }: { prefix: string }) {
{/* glot-message-keys "Common.*.submit" */}
return ;
}
```
## JSX vs Non-JSX Context
Glot automatically detects the context and uses the appropriate comment syntax:
**JSX context** (inside JSX children):
```tsx theme={null}