UniqueTranslationRule is ignored - Laravel 8 about laravel-unique-translation HOT 2 CLOSED

Hello,

I had to refresh my memory for a second, but there is a problem when using nested attribute syntax like post.slug.
You can also use this syntax to submit multiple translations, like slug.en.
So in your case that would becomepost.slug.en, etc.

I have to detect the locale in the validation rule. The way I do this by getting any string after a dot.
Because a locale can be anything, there is no way to distinguish it from a field name.
If you just submit a slug attribute, then there is no dot in the attribute name and the app's locale is used.

I don't know if there is any other way to handle this that supports nested arrays...

Edit:

One workaround that should work is be to add the locale to the form field: name="post[slug][en]"
Then validate post.slug.*

from laravel-unique-translation.

Hello @ivanvermeyen,

Your explanation is very clear, I understood the problem and if I use post.slug.* it works fine! It's an architecture issue on my side: currently, my requests validate the slug for the current language of the user with app()->getLocale(). However, there will be only one form per resource in the back-office, so I actually have to support the validation of several slugs at the same time (the entities are shared between the different languages, only some fields like the title and the slug are translatable).

Thanks for your help, I'll do the corrections on my side 👍 By the way I'll also implement your laravel-localized-routes package for the front-office, it looks great 😎

from laravel-unique-translation.