Laravel - Routes with "sub" views

Question

I am just getting started with Laravel and find the route setup a little confusing. I am trying to create a few pages, that ultimately should have the struture:

domain.com/onboarding
domain.com/onboarding/skip
domain.com/onboarding/skip/anothersubview

etc.

Right now I have:

// Registered and Activated User Routes
Route::group(['middleware' => ['auth', 'activated', 'activity']], function () {

    Route::get('/onboarding', 'UserController@Onboarding')->name('onboarding');
});

Would the solution here (and best practice) be to just add another route inside my Route::group, like:

Route::view('/onboarding/skip', 'onboarding.skip');

Is this the correct way of doing things?

I did it in few projects in the past, I just placed group inside of group inside of group and nothing was wrong, I don't know if it's bad or good habit but every page worked smoothly and everything was fine — bestestefan
– bestestefan, Commented Jul 5, 2018 at 13:26
If it's static pages then Route::view is probably the best solution. Also best practice is to be explicit with your routes. That way you know what navigates where without any surprises. — apokryfos
– apokryfos, Commented Jul 5, 2018 at 13:35

Saurabh Mistry · Accepted Answer · 2018-07-05 13:30:22Z

1

use prefix :

   Route::group(['prefix' => 'onboarding','middleware' => ['auth', 'activated', 'activity']], function () {

        Route::get('/', 'UserController@Onboarding')->name('onboarding');
        Route::get('/skip', 'UserController@OnboardingSkip')->name('onboarding_skip');
        Route::get('/skip/anothersubview', 'UserController@OnboardingSkipSubview')->name('onboarding_skipsubview');

    });

read more here : https://laravel.com/docs/5.6/routing

answered Jul 5, 2018 at 13:30

Saurabh Mistry

13.8k5 gold badges60 silver badges78 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

oliverbj Over a year ago

But what if I have other routes inside the Route::group that have nothing to do with /onboarding

Saurabh Mistry Over a year ago

you need to define separate route , which does not have prefix onboarding

bestestefan · Accepted Answer · 2018-07-05 13:30:34Z

1

The structure I used in a few projects in the past looks like this:

Route::group(['prefix' => 'onboarding'], function(){
    Route::group(['prefix' => 'something'], function(){
        Route::get('/', function(){}); //onboarding/something
        Route::group(['prefix' => 'somethingelse'], function(){
            Route::get('/', function(){}); //onboarding/something/somethingelse
            Route::get('/{id}', function(){}); //onboarding/something/somethingelse/15
        });
    });
});

nesting groups can help you make the easier extendable router because when you realize you need to add some URL in the middle of long structure it would be easier to do it with this concept

answered Jul 5, 2018 at 13:30

bestestefan

8716 silver badges23 bronze badges

Comments

mehlichmeyer · Accepted Answer · 2018-07-05 13:27:04Z

0

You have a web.php file in your routes folder, there you need to add:

Route::get('/subpage', 'controllername@function-name-you-want-to-call');

Hope this helps, if it doesn't let me know

/e: to clarify:

the first part

Route::group(['middleware' => ['auth', 'activated', 'activity']], function () {

is the authentication. Depending on who you want to access this page, you might not need it

answered Jul 5, 2018 at 13:27

mehlichmeyer

1543 silver badges18 bronze badges

Collectives™ on Stack Overflow

Laravel - Routes with "sub" views

3 Answers 3

2 Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related