Add to each custom message in rules parameter for set processing type
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 167
- Forks
- 47
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 3
Description
Default is Error::MESSAGE_TRANSLATE.
For example, Count rule:
public function __construct(
// ...
string $greaterThanMaxMessage = '{Property} must contain at most {max, number} {max, plural, one{item} other{items}}.',
int $greaterThanMaxMessageProcessing = Error::MESSAGE_TRANSLATE,
// ...
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 Count rule constructor shown in the issue and inspect how its custom messages currently use Error::MESSAGE_TRANSLATE. Trace the other rules with custom messages and their tests, then add the processing-type parameter consistently; done means each custom message can select its processing mode while retaining the default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100