eloqnt review — eloqnt/studio

Catch typos, grammar slips and inconsistent terminology in your source strings before they fan out into all your translations.

By default, source strings are only reviewed for objective language errors (spelling and grammar), as well as glossary consistency based on your global styleguide. Intentional wording is protected from unwanted corrections.

eloqnt review
 
✔  Context enrichment complete
✔  Reviewed source strings via eloqnt/engine (hosted)
 
messages/en.json (source locale)
│
│  - "Kcbtmx": "Recieve notifications"
│  + "p4XQ2p": "Receive notifications" (src/components/Settings.tsx)
│  ─┬─────────────────────────────────
│   ╰─ "Recieve" was misspelled
 
messages/
  en.json  3 reviewed, 1 fixed
 
→ Run `eloqnt translate` to translate

Fixes are applied to wherever a string is authored: for messages extracted from your source code, the fix lands at the call site, with the messages file updated to match.

If a fixed string already had translations, they're removed as stale, and you can fill them back in with eloqnt translate.

If you want to enforce additional rules like typographic preferences, you can mention them in styleguide.<sourceLocale>.md. It's recommended to restrict yourself to mechanical rules in this file and avoid tonality instructions that could cause the review command to rewrite source strings unexpectedly.

Flags

--id	string	(Re-)review these message ids (comma-separated)
--config	string	Path to the eloqnt config file (defaults to .eloqnt/config.{ts,mts,js,mjs})
--json	boolean	Output the result as JSON