Check a release before it ships
A QA report catches empty strings, missing languages, broken placeholders, and text that is too long.
A translation file can look finished and still break the product. A placeholder changes in one language. A button label grows past the layout. A key exists in English and nowhere else.
LocalesFS can check that before the release. Call GET /api/projects/:id/qa with a project token or a signed-in token. The report lists each problem with a code, the key, and the language.
The codes are empty, missing, placeholder_mismatch, and max_length. An empty string is reported on its own. The source language is left out of the target checks, so English is not flagged for missing English.
Use the count in the report as a gate. If issue_count is above zero, stop the release and open a review task for the strings that failed. The same project can send a signed webhook when a key or a translation changes, so the check can run again without a person watching the dashboard.
The report does not rewrite the copy. It tells you what to fix. The wording is still decided on the key.
Demo
Request a translation
Spanish, French, and German are already saved for this article. The request reads that copy. It does not call a translation API.
Showing the saved English.