Separate technical and non-technical error messages
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/issues/492#issuecomment-1422471435. This was discussed before. The topic raised again by @cebe.
Related - #526.
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 by reading the discussion extracted from yiisoft/validator#492, including comment 1422471435, and then review related issue #526. The issue does not name files, entry points, or acceptance criteria; clarify the intended technical/non-technical message split and its expected behavior before implementation.
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
- Needs clarification
- Newbie friendliness
- 25/100