php - Laravel Route - Nested Resource Controllers without intermediate page -


i have 2 controllers - chcontroller & fillcontroller . chcontroller works fine.

route::resource('c', 'chcontroller');      |        | get|head | c                | c.index         | app\http\controllers\chcontroller@index     |            |     |        | get|head | c/create         | c.create        | app\http\controllers\chcontroller@create    |            |     |        | post     | c                | c.store         | app\http\controllers\chcontroller@store     |            |     |        | get|head | c/{c}            | c.show          | app\http\controllers\chcontroller@show      |            |     |        | get|head | c/{c}/edit       | c.edit          | app\http\controllers\chcontroller@edit      |            |     |        | put      | c/{c}            | c.update        | app\http\controllers\chcontroller@update    |            |     |        | patch    | c/{c}            |                 | app\http\controllers\chcontroller@update    |            |     |        | delete   | c/{c}            | c.destroy       | app\http\controllers\chcontroller@destroy   |            |

but need nested fillcontroller (f), like:

/c/{c}/create /c/{c}/{f} /c/{c}/{f}/show /c/{c}/{f}/edit  // etc...

i tried:

route::group(['prefix' => 'c/{c}'], function () {     route::resource('{f}', 'fillcontroller'); });       |        | get|head | c/{c}/{f}            | c.{c}.{f}.index   | app\http\controllers\fillcontroller@index   |            |     |        | get|head | c/{c}/{f}/create     | c.{c}.{f}.create  | app\http\controllers\fillcontroller@create  |            |     |        | post     | c/{c}/{f}            | c.{c}.{f}.store   | app\http\controllers\fillcontroller@store   |            |     |        | get|head | c/{c}/{f}/{{f}}      | c.{c}.{f}.show    | app\http\controllers\fillcontroller@show    |            |     |        | get|head | c/{c}/{f}/{{f}}/edit | c.{c}.{f}.edit    | app\http\controllers\fillcontroller@edit    |            |     |        | put      | c/{c}/{f}/{{f}}      | c.{c}.{f}.update  | app\http\controllers\fillcontroller@update  |            |     |        | patch    | c/{c}/{f}/{{f}}      |                   | app\http\controllers\fillcontroller@update  |            |     |        | delete   | c/{c}/{f}/{{f}}      | c.{c}.{f}.destroy | app\http\controllers\fillcontroller@destroy |            |   route::group(['prefix' => 'c/{c}'], function () {     route::resource('f', 'fillcontroller'); });       |        | get|head | c/{c}/f          | c.{c}.f.index   | app\http\controllers\fillcontroller@index   |            |     |        | get|head | c/{c}/f/create   | c.{c}.f.create  | app\http\controllers\fillcontroller@create  |            |     |        | post     | c/{c}/f          | c.{c}.f.store   | app\http\controllers\fillcontroller@store   |            |     |        | get|head | c/{c}/f/{f}      | c.{c}.f.show    | app\http\controllers\fillcontroller@show    |            |     |        | get|head | c/{c}/f/{f}/edit | c.{c}.f.edit    | app\http\controllers\fillcontroller@edit    |            |     |        | put      | c/{c}/f/{f}      | c.{c}.f.update  | app\http\controllers\fillcontroller@update  |            |     |        | patch    | c/{c}/f/{f}      |                 | app\http\controllers\fillcontroller@update  |            |     |        | delete   | c/{c}/f/{f}      | c.{c}.f.destroy | app\http\controllers\fillcontroller@destroy |            |

all of them makes intermediate page /f/ , don't need.

the close that:

route::group(['prefix' => 'c/{c}'], function () {     route::resource('', 'fillcontroller'); });      |        | get|head | c/{c}/create  | c.{c}..create  | app\http\controllers\fillcontroller@create  |            |     |        | post     | c/{c}         | c.{c}..store   | app\http\controllers\fillcontroller@store   |            |     |        | get|head | c/{c}/{}      | c.{c}..show    | app\http\controllers\fillcontroller@show    |            |     |        | get|head | c/{c}/{}/edit | c.{c}..edit    | app\http\controllers\fillcontroller@edit    |            |     |        | put      | c/{c}/{}      | c.{c}..update  | app\http\controllers\fillcontroller@update  |            |     |        | patch    | c/{c}/{}      |                | app\http\controllers\fillcontroller@update  |            |     |        | delete   | c/{c}/{}      | c.{c}..destroy | app\http\controllers\fillcontroller@destroy |            |

but router doesn't know {f} parameter.

first of f not an intermediate page refer it, it's uri segment. , it's way go, because saying subresource (f) being accessed. suggest stick it.

now if still want go way, can achieve 1 exception. can't have index route f subresource in naming scheme because overwrite show c resource. 

route::group(['prefix' => 'c/{c}'], function () {     // can't have because overwrite c.show     // route::get('/', ['as' => 'f.index', 'uses' => 'fillcontroller@index']);     route::get('/create', ['as' => 'f.create', 'uses' => 'fillcontroller@create']);     route::post('/', ['as' => 'f.store', 'uses' => 'fillcontroller@store']);     route::get('/{f}/edit', ['as' => 'f.edit', 'uses' => 'fillcontroller@edit']);     route::put('/{f}', ['as' => 'f.update', 'uses' => 'fillcontroller@update']);     route::patch('/{f}', 'fillcontroller@update');     route::delete('/{f}', ['as' => 'f.destroy', 'uses' => 'fillcontroller@destroy']); }); 
 |   | get|head | c              | c.index   | app\http\controllers\chcontroller@index     |     | |   | get|head | c/create       | c.create  | app\http\controllers\chcontroller@create    |     | |   | post     | c              | c.store   | app\http\controllers\chcontroller@store     |     | |   | get|head | c/{c}          | f.index   | app\http\controllers\fillcontroller@index   |     | |   | get|head | c/{c}/edit     | c.edit    | app\http\controllers\chcontroller@edit      |     | |   | put      | c/{c}          | c.update  | app\http\controllers\chcontroller@update    |     | |   | patch    | c/{c}          |           | app\http\controllers\chcontroller@update    |     | |   | delete   | c/{c}          | c.destroy | app\http\controllers\chcontroller@destroy   |     | |   | get|head | c/{c}/create   | f.create  | app\http\controllers\fillcontroller@create  |     | |   | post     | c/{c}          | f.store   | app\http\controllers\fillcontroller@store   |     | |   | get|head | c/{c}/{f}/edit | f.edit    | app\http\controllers\fillcontroller@edit    |     | |   | put      | c/{c}/{f}      | f.update  | app\http\controllers\fillcontroller@update  |     | |   | patch    | c/{c}/{f}      |           | app\http\controllers\fillcontroller@update  |     | |   | delete   | c/{c}/{f}      | f.destroy | app\http\controllers\fillcontroller@destroy |     |

Comments

Post a Comment

Popular posts from this blog

angularjs - ADAL JS Angular- WebAPI add a new role claim to the token -

i have created angular spa webapi backend using adal js authentication.as there no roles in ad, need manually add role claims in order give users access different api controllers. the roles stored in database. expecting inject claim through call webapi after authentication ad. webapi code might this. identity.addclaim(new claim("role", "user")); var ticket = new authenticationticket(identity, props); var accesstoken = startup.oauthbeareroptions.accesstokenformat.protect(ticket); is possible replace adal idtoken new token? is viable solution or there other better way handle this? as initial token generated azuread, possible edit token add new claim? appreciated. graph api supporting group claims. see here: http://justazure.com/azure-active-directory-part-4-group-claims/ if @ examples on page, users assigned groups , app can check group in claims. in current version of portal, need app manifest , modify it.
Read more

node.js - Using Node without global install -

i'm working on few node & electron (atom shell) projects , i'm curious how them work without user having install node globally. i've seen few applications including node directory in project contains node.exe binary. how go setting node project use binary? edit: thought should add, i've searched everywhere answer this, unrelated results.
Read more

php - CakePHP HttpSockets send array of paramms -

i problem when make request (i can request). $link = 'http://uri/path/?param1=1&sid=2&sid=3&sid=4' $http = $httpsocket = new httpsocket(); $res = $httpsocket->get($link); if check request pr($http); i see : [line] => /url/path/?param1=1&sid%5b0%5d=2&sid%5b1%5d=3&sid%5b2%5d=4 http/1.1 and i'm getting empty response because server doesn't know parameters sid%5b0%5d=2 when try send parameters array : $data = array('param1' => '1', 'sid' => array('2','3', '4')); i see same changes %5b0%5d - additional indexes. how fix it? unfortunately , can not change server side, if send request in browser, i'll normal response in json format. when make request, can parameters this: $param1 = $_get['param1']; $sid= $_get['sid']; tip: use diferente names parameters. have multiples sid. use sid1, sid2, sid3... update: can parameters this:...
Read more