-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
Validation problem with "*.name" after update from Laravel 5.2.30 to next versions #14232
Comments
@themsaid any ideas? |
@migoca your validation rules here state that for every form field there should be array members with keys I don't think this behaviour is recent, are you sure it was working differently in 5.2.30? Anyways I suggest you use a structure like this:
|
Yes @themsaid in 5.2.30 these validation rules works like I expected, but when i update to 5.2.31 ..5.2.39 and fill these fields the form don't pass the validation rules and return with: Maybe was for this pull request #13224 merged in 5.2.31, fixing data_set issue. I like the structure that you have suggested, I will try! Thanks |
@migoca I'm not sure if that PR caused the change in behaviour, but anyways I think the current behaviour makes sense, when you use |
Thanks @themsaid for your help! You are right, the current behavior makes more sense. |
After upgrading Laravel from 5.2.30 to .31 and next versions I have problem with these types of validations:
I use this to validate for multiple languages: es.name, en.name, it.name, etc. But with the update the result is:
The _token.name field is required.
The _token.slug is required.
In my form i have:
The text was updated successfully, but these errors were encountered: