Route::resource not translate url about localization HOT 7 CLOSED

The Route::resource() is not in Localization package scope.

As you can see there is no Route::transResource, and the routes.users is not going to be translated.

Try to be explicit with your routes and use the transGet, transPost, transDelete ... methods, that will fix your problem.

Check : #9

from localization.

Do you plan to add this feature (Route::transResource) to the next commit?

from localization.

I don't know 😕 , and to be honest with you, it's not a good idea.

The Route::resource may unintentionally take precedence over your supplemental routes.

And Route::resource + The Localization package = Nightmare.

If you want my advise, try to be explicit with your routes. It's like you're drawing paths (roads/routes) to your controllers.

from localization.

Ok, I understand... I will change my code. Thanks a lot!

from localization.

You're welcome 👍

from localization.

I think that transResource should be implemented, as Laravel provides Route::resource your package should support it, or at least provide a method like LaravelLocalization::transRoute that allows you to translate the route on the fly as on mcamara and make the resource work.

By not supporting Route::transResource you are discouraging the use of Laravel's good practices, which suggests using Route::resource in case of certain needs.

How can I help?

from localization.

Hi @fede91it,

TLDR: Feel free to make a PR with tests 👍

TBH, i'm not fan about the Route::resource because i prefer to create routes explicitly.

This is why the transResource method is not available.

By not supporting Route::transResource you are discouraging the use of Laravel's good practices, which suggests using Route::resource in case of certain needs.

I don't think this considered as a Laravel's good practices, this is just what we call a magic functionnality that allows you to do a lot of things & faster with little efforts.

The idea behind Route::resource method is to create the RESTful routes.
You can achieve that by using explicit routes

Wiki: https://en.wikipedia.org/wiki/Representational_state_transfer

My top 4 benefits about using explicit routes are:

• 100% Total control of what i'm doing.
• Easy route customization (without cheking the laravel's documentations or forums).
• By reading the routes file(s), i have a clear view of the available routes without using the php artisan route:list command.
• Prevents me to be a lazy person 😝

This is an example how i use & structure the routes in a OOP way in one of my projects:

• RouteServiceProvider
• UsersRoutes

This is just my opinion and i'm not against your suggestion, so feel free to make a PR to add this feature.

from localization.