Separate similar error messages' translations for different rules
Open
Nobody has claimed this yet.
status:under discussion
type:enhancement
- Dominant language
- PHP
- Stars
- 167
- Forks
- 47
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 3
Description
Extracted from https://github.com/yiisoft/validator/pull/514#discussion_r1090048741.
Related: #525.
Problem: changing translation for incorrect type message might affect multiple rules.
Possible solution: use keys for translation instead, something like "json.incorrectInputMessage".
This can be helpful when a user wants to hide technical details with broader messages for example.
Contributor guide
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 with the discussion in PR #514 and related issue #525, then trace how translations for similar rule error messages are selected. Separate translation keys so changing one rule does not affect others, while allowing users to replace technical details with broader messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100