Level 41
It doesn't matter what company the event belongs to, why not make the url event/1/edit ? without "/compmany/1/"
Jan 25, 2015
6
Level 30
Quick Question how to handle id`s in the url
For example:
A User has many companies and each companies has many events.
If i edit one of my companies the url would be ../company/1/edit
Ok so far so good .. now i added a event to this company. The url would be ../compmany/1/event/create
Now the "tricky" part if i want to edit this event the url would be:
../company/1/event/1/edit
But this of course does not work because i cant give two ID`s to the routes.php
Should i go for a slug ? Or the better question: How are you guys handle this ?
Level 52
I suppose you use nested resources so you get ../company/1/event/1/edit in routes. You can exclude this route to simplify url as said @RachidLaasri.
Level 53
@hostianer And what makes you think you can't give 2 ids to the route ?
Level 52
@JarekTkaczyk I think he wanted to say that he doesn't want to put 2 ids to the route.
Level 65
Have one resource for events and one resource for companies. When you edit the event, you can always display the company it's attached to in the form/page.
Level 56
You are doing it fine with the two ids in the url. It is always useful to have the parent id in the url.
Route::get('companies/{company_id}/events/{event_id}/edit', ...);
public function edit($category_id, $event_id)
{
// your edit action
}
Please or to participate in this conversation.