Separate getting of formatted 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
A concept suggested by @xepozz.
$messages = new ErrorMessages();
// index by
$messages->indexByKey();
$messages->indexByParameter();
$messages->indexBy($closure);
// select
$messages->firstErrors();
$messages->firstError();
$messages->all();
// filter errors
$messages->filter($closure);
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 reviewing the proposed ErrorMessages concept and its indexByKey(), indexByParameter(), indexBy(), firstErrors(), firstError(), all(), and filter() operations. Define the intended behavior and scope for separating formatted error-message retrieval before identifying the affected validator code and tests; done means the design is implemented and the selection, indexing, and filtering behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100