Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature: accsess eachPrefix in error messages #2461

Open
MR-Mostafa opened this issue Apr 13, 2024 · 0 comments
Open

feature: accsess eachPrefix in error messages #2461

MR-Mostafa opened this issue Apr 13, 2024 · 0 comments
Labels
flag: needs discussion Issues which needs discussion before implementation. type: feature Issues related to new features.

Comments

@MR-Mostafa
Copy link

Description

When validating an object, we cannot directly access the eachPrefix in the error message. Consequently, when we modify the error message, the value of eachPrefix always appears at the beginning of the message.
For example, if we change the validation message forIsNotEmpty to The The value of field $property should not be empty., the resulting output will be: eachPrefix The value of field $property should not be empty. But the truth is that it should be like this: The value of field $eachPrefix.$property should not be empty.

Proposed solution

Accsess to eachPrefix like $property or in ValidationArguments.

@MR-Mostafa MR-Mostafa added flag: needs discussion Issues which needs discussion before implementation. type: feature Issues related to new features. labels Apr 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flag: needs discussion Issues which needs discussion before implementation. type: feature Issues related to new features.
Development

No branches or pull requests

1 participant