Why is the default value for `t` hardcoded as empty string?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 798
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
What if I want it to return the key name, instead of an empty string? There's no way to distinguish between a value that is genuinely an empty string, and a missing key.
The point is, the default value for missing keys shouldn't be hardcoded.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the translation lookup entry point and reviewing any existing tests for missing keys. Clarify whether the desired behavior is a configurable fallback, returning the key name, or another API change, then define tests that distinguish missing keys from translations whose value is an empty string.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- internationalization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100