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
Custom translator singleton are overriding by default translator #31067
Comments
I'm not sure how these changes break that package. We'll need some more info on this to determine what has broken. |
I'm going to try and take a look at this tonight. |
@elvinas21, I have a fix coming for this so I think the issue can be closed. |
It could be caused when 3rd party is loading the service provider as eagered while Laravel translator is deferred. |
Hi @elvinas21, I just pushed a fix to master. Any chance you can pull down and let me know if the issue is resolved? Thanks, |
Hi @joedixon, i will check, and let you know the results. |
Description:
After I upgraded my Laravel from v6.9.0 to v6.10.0 third party translation library stopped working.
In Laravel v6.9.0 firstly are registering Laravel native 'translator' singleton and after that it registering third party libraries singletons, but in Laravel v6.10.0 firstly are registered third party libraries singleton named 'translator' and after that it will be overridden by Laravel native 'translator' singleton.
It could be caused by this changes: #31009 @GrahamCampbell please check it. Thanks.
Steps To Reproduce:
Use one of the package which extends translations functionality and register translator singleton
I'm using this https://github.com/joedixon/laravel-translation library which takes translations from database
The text was updated successfully, but these errors were encountered: