Warn on / visualize leading/trailing whitespaces in key names [UI] #3359
Description
1. Problem
When users copy-paste keys into Tolgee, they can accidentally include leading or trailing whitespaces.
These invisible characters are hard to notice and can lead to:
- Missing or mismatched keys
- Confusing behavior that looks like bugs
- Support requests and user frustration
From a business perspective, this impacts perceived product maturity and stability. Reducing this friction improves trust in Tolgee and can lower churn and support load.
2. Appetite
1 day
This should be a small, contained UX improvement with minimal risk and no deep architectural changes.
3. Solution
Add lightweight UI safeguards when users create or edit keys.
At a high level:
- Detect leading/trailing whitespaces in keys on save
- Warn the user before persisting such a key
- Make the whitespace visible so users understand what’s wrong
The goal is not to block advanced users entirely, but to make the issue obvious and intentional.
4. Rabbit Holes
Potential risks or complexities
- Deciding the best visualization for whitespace that is clear but not distracting
- Ensuring consistent behavior across key creation and key editing (should not be warned when key contained leading/trailing whitespaces before)
- Avoiding false positives (e.g. internal spaces should not be flagged)
No major technical unknowns expected.
5. No-Goes
Explicitly out of scope
- Backend validation or enforcement
- Handling imports, API endpoints, or bulk operations
- Automatic trimming or mutation of user input without confirmation
This pitch is UI-only and interactive flows only.
6. Success Criteria
How we know this worked
- Users clearly understand when a key contains leading/trailing whitespace
- Support requests related to “missing keys” or whitespace confusion disappear
- Users no longer feel confused or surprised by whitespace-related issues
- The feature feels like a polish improvement, not an obstruction