-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Package seems to cause translation errors in other packages #59
Comments
Thanks for reporting. According to this comment the translation should not be used before setting a current locale. I checked this and noticed the locale is already set when this code runs. Can't think of an other solution as to pass static text error messages to the Illuminate\Validation\Factory::extend() method, which contradicts the whole translation logic. Any other thoughts on this? |
Still happening. Using it in combination with Laravel nova and all of my translation suddenly don't work. When I uninstall the package, they do. |
Just noticed that it all has to do with calling that translater too early.
|
Thanks, I just tested your approach with Laravel However, I cannot reproduce the error with the setup mentioned above. |
It seems that this package causes translation errors in Laravel Nova (see this issue laravel/nova-issues#4192).
By calling a translation in a constructor the incorrect locale is set for the App (laravel/nova-issues#4192 (comment))
I think this is what is happening with this package in the file
validation/src/Laravel/ValidationServiceProvider.php
.From the
boot()
function$this->getErrorMessage()
is called and this callsreturn $this->app['translator']->get('validation::validation.' . $rulename);
. (https://github.com/Intervention/validation/blob/master/src/Laravel/ValidationServiceProvider.php#L48)When I comment this out or replace it with
return '';
the translation errors in Laravel Nova disappear.I am using php8, laravel/framework 9.26.1, laravel/nova 4.13.0, intervention/validation 3.2.0
The text was updated successfully, but these errors were encountered: