Laravel RESTful controller add parameter to create

Question

I am trying to use Laravel 5.2's RESTful resource controllers. However, when moving from my index to create, I would like to pass a parameter as the create page should be partially filled in.

edit The form that will be 'created' will have populated fields from the database already. So the create should take the id from the user that is clicked in the index.

My temporary solution:

Route::get('consultation/{id}', 'ConsultationController@create');
Route::resource('consultation', 'ConsultationController', ['except' => ['create']]);

Is there a way to add this to an options array in the same line as resource?

Thanks

Edit: I suppose in this case, my store would also need the same {id} parameter.

sorry but i dont get what you mean, you want to pass something from the view to be shown in the create view? from where you will get it? user input in index or what? can you explain better please — Achraf Khouadja
– Achraf Khouadja, Commented May 9, 2016 at 2:27
I edited my post. The info will be pulled from the database based on the id being passed in. I have an index with clickable rows, when that row is clicked, it should redirect to the create resource but pass in an id, by default Laravel's RESTful controller has create with no parameters. — Arthur
– Arthur, Commented May 9, 2016 at 2:34
you can use a form in the index with a methd=get with a hidden input instead of <a> and then access the data via $request->input('') in the @create function and return it with it — Achraf Khouadja
– Achraf Khouadja, Commented May 9, 2016 at 2:38

Hammerbot · Accepted Answer · 2016-05-09 03:11:40Z

4

I was also curious about that but I think that the Laravel Documentation is pretty clear about this:

If it becomes necessary to add additional routes to a resource controller beyond the default resource routes, you should define those routes before your call to Route::resource

And they add the following, meaning for me that if you want to override a defined route, you just need to put the definition on top of the Route::resource() definition.

otherwise, the routes defined by the resource method may unintentionally take precedence over your supplemental routes

EDIT

After better understanding the question, I would let the restful controller as is, and create a new route like /user/{user-id}/consultations/create that is much more "restful" like.

edited May 9, 2016 at 3:11

answered May 9, 2016 at 2:39

Hammerbot

16.5k13 gold badges67 silver badges109 bronze badges

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

5 Comments

Arthur Over a year ago

The reason I do not want to use the show() method is because I would like the create to be partially filled in based on the {id}, and the rest be filled in by the user. Where as I would like show() to be the fully filled out form. Thank you for the answer, I will probably just keep it above the resource() definition.

Hammerbot Over a year ago

I understand your point, but if you use consultation/{id} as a route, this will override your show() method, am I wrong? You could create a route like consultation/create/{id} or something

Arthur Over a year ago

You are right. I'll change my route to that. Thanks

Hammerbot Over a year ago

Ho, and if this is a user id, I would rather make a route like: /user/{user-id}/consultations/create that is, in my opinion much more "restful"

Arthur Over a year ago

I'll take that into consideration - overall structure is a bit messy at the moment ha. Thanks again.

Collectives™ on Stack Overflow

Laravel RESTful controller add parameter to create

1 Answer 1

5 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

5 Comments

Your Answer

Sign up or log in

Post as a guest

Related