Tutorial

Find problems before a release

A language card counts the values with a QA finding, and the count opens the editor on exactly those. Two of them here — a renamed placeholder and a translated product name — fixed until the count is gone.

4 minutes · 5 steps Updated

  1. Step 01

    Read the count on the language card

    Open the project — under its progress bar the German card says how many of its values on main have a QA finding, here 2 with issues.

    How it works: The Editor

  2. Step 02

    Open the values with issues

    Click the count: the German editor opens with the Has issues filter already set, and the key tree lists only the two keys with a finding.

    How it works: The Editor

  3. Step 03

    Fix a renamed placeholder

    Click shop.product.price — the badge says {price} was renamed to {preis}, so put the original name back, because the app fills in {price} and nothing else.

    How it works: Placeholder Validation for Translations

  4. Step 04

    Keep a protected term

    Click shop.checkout.club — Example Club is marked in the original because the project’s owner protects it under Settings, and the badge says the German value dropped it.

    How it works: The Editor

  5. Step 05

    Fix it, and the count goes

    Write the term as it stands and the badge goes — with both values corrected, the key tree under Has issues is empty and the German card no longer shows a count.

    How it works: The Editor

Where to go from here

The documentation covers everything this walkthrough skipped, and the other tutorials take the next task from here.

Do it with your own files.

Start on the free tier with the locale files you already have.

Create your account