Too many messages about laravel-unique-translation

[ivanvermeyen]

Hi,

I see your point :)
This behavior was actually a request some time ago (#1).
But there may well be a decent solution to handle both use cases.
I'll have to dig back in and think about how to do this though.

[Xinecraft]

If we use something like https://formvuelar.netlify.com/ this bug will get annoying and hard to fix I think from the frontend side.

[ivanvermeyen]

Hello,

I agree that always returning both single and array error messages is not optimal after all and it's also not how Laravel handles form errors by default.

I will revert back to only returning relevant messages and try to work out some option to change the behavior for use cases as described in #1 by @ctf0) .

This will need to be a new major version, since it might have an impact on existing implementations.

[ivanvermeyen]

I pushed an update to dev-master that uses Laravel's default behavior.
Only one error will be returned per form attribute:

Form Field	Validation Rule	Error Key
slug	'slug' => 'unique_translation:table,column'	slug
slug[en]	'slug.*' => 'unique_translation:table,column'	slug.en

If you could try or review it, I will tag a new release and then see if I can add some options for extra error messages... 👌

[ivanvermeyen]

Tagged in 3.0.0 👍