yii2-nested-rest
, (*1)
Adds nested resources routing support along with related actions and relationship handlers to the Yii RESTful API framework., (*2)
How It Works
This extension doesn't replace any of the built-in REST components. It is about a collection of helper actions and a custom UrlRule class designed to be used along with the default one:, (*3)
'rules' => [
[
// Yii defaults REST UrlRule class
'class' => 'yii\rest\UrlRule',
'controller' => ['team','player','skill'],
],
[
// The custom UrlRule class
'class' => 'tunecino\nestedrest\UrlRule',
'modelClass' => 'app\models\Team',
'relations' => ['players'],
],
[
'class' => 'tunecino\nestedrest\UrlRule',
'modelClass' => 'app\models\Player',
'relations' => ['team','skills'],
],
]
To explain how it works, lets better go through an example:, (*4)
If within the previous configurations we expect team and player to share a one-to-many relationship while player and skill shares a many-to-many relation within a junction table and having an extra column called level in that junction table then this extension may help achieving the following HTTP requests:, (*5)
# get the players 2, 3 and 4 from team 1
GET /teams/1/players/2,3,4
# list all skills of player 5
GET /players/5/skills
# put the players 5 and 6 in team 1
PUT /teams/1/players/5,6
# create a new player and put him in team 1
POST /teams/1/players
{name: 'Didier Drogba', position: 'FC'}
# create a new skill called 'dribble' and assign it to player 9
# with a related level of 10 ('level' should be stored in the junction table)
POST /players/9/skills
{name: 'dribble', level: 10}
# update the 'level' attribute in the junction table related to player 9 and skill 2
PUT /players/9/skills/2
{level: 11}
# unlink skill 3 and player 2
DELETE /players/2/skills/3
# get all players out of team 2
DELETE /teams/2/players
Installation
The preferred way to install this extension is through composer., (*6)
Either run, (*7)
$ composer require tunecino/yii2-nested-rest
or add, (*8)
"tunecino/yii2-nested-rest": "*"
to the require section of your composer.json file., (*9)
Configuration
By default, all the properties used by the custom UrlRule class in this extension will be used to generate multiple instances of the built-in yii\rest\UrlRule so basically both classes are sharing similar configurations., (*10)
Those are all the possible configurations that may be set to the UrlManager in the app config file:, (*11)
'rules' => [
[
/**
* the custom UrlRule class
*/
'class' => 'tunecino\nestedrest\UrlRule', /* required */
/**
* the model class name
*/
'modelClass' => 'app\models\Player', /* required */
/**
* relations names to be nested with this model
* they should be already defined in the model's Active Record class.
* check the below section for more about advanced configurations.
*/
'relations' => ['team','skills'], /* required */
/**
* used to generate the 'prefix'.
* default: the model name pluralized
*/
'resourceName' => 'players', /* optional */
/**
* also used with 'prefix'. is the expected foreign key.
* default: $model_name . '_id'
*/
'linkAttribute' => 'player_id', /* optional */
/**
* building related rules using 'controller => ['teams' => 'v1/team']'
* instead of 'controller => ['team']'
*/
'modulePrefix' => 'v1', /* optional */
/**
* the default list of tokens that should be replaced for each pattern.
*/
'tokens' => [ /* optional */
'{id}' => '<id:\\d[\\d,]*>',
'{IDs}' => '<IDs:\\d[\\d,]*>',
],
/**
* The Regular Expressions Syntax used to parse the id of the main resource from url.
* For example, in the following final rule, $linkAttributePattern is default to that `\d+` to parse $brand_id value:
*
* GET,HEAD v1/brands/<brand_id:\d+>/items/<IDs:\d[\d,]*>
*
* While that works fine with digital IDs, in a system using a different format, like uuid for example,
* you may use $linkAttributePattern to define different patterns. Something like this maybe:
*
* [
* // Nested Rules Brand
* 'class' => 'tunecino\nestedrest\UrlRule',
* 'modelClass' => 'app\modules\v1\models\Brand',
* 'modulePrefix' => 'v1',
* 'resourceName' => 'v1/brands',
* 'relations' => ['items'],
* 'tokens' => [
* '{id}' => '<id:[a-f0-9]{8}\\-[a-f0-9]{4}\\-4[a-f0-9]{3}\\-(8|9|a|b)[a-f0-9]{3}\\-[a-f0-9]{12}>',
* '{IDs}' => '<IDs:([a-f0-9]{8}\\-[a-f0-9]{4}\\-4[a-f0-9]{3}\\-(8|9|a|b)[a-f0-9]{3}\\-[a-f0-9]{12}(?:,|$))*>',
* ],
* 'linkAttributePattern' => '[a-f0-9]{8}\\-[a-f0-9]{4}\\-4[a-f0-9]{3}\\-(8|9|a|b)[a-f0-9]{3}\\-[a-f0-9]{12}',
* ],
*/
'linkAttributePattern' => '\d+', /* optional */
/**
* the default list of patterns. they may all be overridden here
* or just edited within $only, $except and $extraPatterns properties
*/
'patterns' => [ /* optional */
'GET,HEAD {IDs}' => 'nested-view',
'GET,HEAD' => 'nested-index',
'POST' => 'nested-create',
'PUT {IDs}' => 'nested-link',
'DELETE {IDs}' => 'nested-unlink',
'DELETE' => 'nested-unlink-all',
'{id}' => 'options',
'' => 'options',
],
/**
* list of acceptable actions.
*/
'only' => [], /* optional */
/**
* actions that should be excluded.
*/
'except' => [], /* optional */
/**
* supporting extra actions in addition to those listed in $patterns.
*/
'extraPatterns' => [] /* optional */
],
]
As you may notice; by default; $patterns is pointing to 6 new actions different from the basic CRUD actions attached to the ActiveController class. Those are the helper actions included in this extension and you will need to manually declare them whenever needed inside your controllers or inside a BaseController from which all others should extend. Also note that by default we are expecting an OptionsAction attached to the related controller. That should be the case for any controller extending ActiveController or its child controllers. Otherwise, you should also implement \yii\rest\OptionsAction., (*12)
The following is an example of a full implementation within the controller::actions() function:, (*13)
public function actions()
{
$actions = parent::actions();
$actions['nested-index'] = [
'class' => 'tunecino\nestedrest\IndexAction', /* required */
'modelClass' => $this->modelClass, /* required */
'checkAccess' => [$this, 'checkAccess'], /* optional */
];
$actions['nested-view'] = [
'class' => 'tunecino\nestedrest\ViewAction', /* required */
'modelClass' => $this->modelClass, /* required */
'checkAccess' => [$this, 'checkAccess'], /* optional */
];
$actions['nested-create'] = [
'class' => 'tunecino\nestedrest\CreateAction', /* required */
'modelClass' => $this->modelClass, /* required */
'checkAccess' => [$this, 'checkAccess'], /* optional */
/**
* the scenario to be assigned to the new model before it is validated and saved.
*/
'scenario' => 'default', /* optional */
/**
* the scenario to be assigned to the model class responsible
* of handling the data stored in the juction table.
*/
'viaScenario' => 'default', /* optional */
/**
* expect junction table related data to be wrapped in a sub object key in the body request.
* In the example we gave above we would need to do :
* POST {name: 'dribble', related: {level: 10}}
* instead of {name: 'dribble', level: 10}
*/
'viaWrapper' => 'related' /* optional */
];
$actions['nested-link'] = [
'class' => 'tunecino\nestedrest\LinkAction', /* required */
'modelClass' => $this->modelClass, /* required */
'checkAccess' => [$this, 'checkAccess'], /* optional */
/**
* the scenario to be assigned to the model class responsible
* of handling the data stored in the juction table.
*/
'viaScenario' => 'default', /* optional */
];
$actions['nested-unlink'] = [
'class' => 'tunecino\nestedrest\UnlinkAction', /* required */
'modelClass' => $this->modelClass, /* required */
'checkAccess' => [$this, 'checkAccess'], /* optional */
];
$actions['nested-unlink-all'] = [
'class' => 'tunecino\nestedrest\UnlinkAllAction', /* required */
'modelClass' => $this->modelClass, /* required */
'checkAccess' => [$this, 'checkAccess'], /* optional */
];
return $actions;
}
What you need to know
1. This doesn't support composite keys. In fact one of my main concerns when building this extension was to figure out a clean alternative to not have to build resources for composite keys related models like the ones mapping a junction table. check the example provided in section 8. for more details., (*14)
2. When defining relation names in the config file they should match the method names implemented inside your model (see Declaring Relations section in the Yii guide for more details).
This extension will do the check and will throw an InvalidConfigException if they don't match but for performance reasons (check this) and because it make no sense to keep doing the same verification with each request when you already did correctly set a list of relations, this extension won't do that DB schema parsing anymore when the application is in production mode. in other words verification is made only whenYII_DEBUG is true., (*15)
3. By default, when you specify a relation 'abc' in the $relation property, its related name expected to be used in the URL endpoint should be 'abcs' (pluralized) while its controller is expected to be AbcController. This can be changed by configuring the $relation property to explicitly specify how to map the relation name used in endpoint URLs to its related controller ID.
For example, if we had a relation defined inside the Team model class within a getJuniorCoaches() method we can do the following:, (*16)
// GET /players/1/junior-coaches => should route to 'JuniorCoachController'
'relations' => ['players','juniorCoaches'] // how it works by default
// GET /players/1/junior-coaches => should route to 'JuniorCoachesController'
'relations' => [
'players',
'juniorCoaches' => 'junior-coaches' // different controller name
]
// GET /players/1/juniors => should route to 'JuniorCoachesController'
'relations' => [
'players',
'juniorCoaches' => ['juniors' => 'junior-coaches'] // different endpoint name and different controller name
]
4. When it comes to linking many-to-many relations with extra columns in a junction table it is highly recommended to use via() instead of viaTable() so the intermediate class can be used by this extension to validate related attributes instead of using link() and saving data without performing the appropriate validations. Refer to the Relations via a Junction Table section in the Yii guide for more details., (*17)
5. When you do:, (*18)
POST /players/9/skills
{name: 'dribble', level: 10}
and the 'name' attribute is supposed to be loaded and saved along with the new created model while 'level' should be added in a related junction table. Then you should know this:, (*19)
-
If relation between both models is defined within via() , Yii::$app->request->bodyParams will be populated to to both models using the load() method:, (*20)
$model->load($bodyParams);
$viaModel->load($bodyParams);
/* Scenarios can also be assigned to both models. when attaching actions. see configuration section */
-
If relation is defined within viaTable() instead the script will try to do some guessing., (*21)
So when unexpected results happens or when attribute names are similar in model class and junction related class, it would be recommended to set the viaWrapper property. See the 'nested-create' action in the configuration section for more details., (*22)
6. When unlinking data, if the relation type between both models is many_to_many related row in the junction table will be removed. Otherwise the concerned foreign key attribute will be set to NULL in its related column in database., (*23)
7. When a successful linking or unlinking request happens, a 204 response should be expected while a 304 response should tell that no change has been made like when asking to link two already linked models.
When you try to link 2 models sharing a many_to_many relationship and both models are already linked no extra row will be added to related junction table: If the bodyRequest is empty you'll get a 304 response otherwise the bodyRequest content will be used to update the extra attributes found in the junction table and you'll get a 204 headers response., (*24)
8. When performing any HTTP request; lets say as example GET /players/9/skills/2; The custom UrlRule will redirect it by default to the route skill/nested-view (or other depending on your patterns) with those 4 extra attributes added to Yii::$app->request->queryParams:, (*25)
relativeClass = 'app/models/player'; // the class name of the relative model
relationName = 'skills'; // the one you did set in rules configuration.
linkAttribute = 'player_id'; // the foreign key attribute name.
player_id = 9; // the foreign key attribute and its value
Those may be useful when building your own actions or doing extra things like for example if we add the following inside app/models/skill :, (*26)
// junction table related method. usually auto generated by gii.
public function getSkillHasPlayers()
{
return $this->hasMany(SkillHasPlayer::className(), ['skill_id' => 'id']);
}
protected function getSharedData()
{
$params = Yii::$app->request->queryParams;
$player_id = empty($params['player_id']) ? null : $params['player_id'];
return ($player_id) ? $this->getSkillHasPlayers()
->where(['player_id' => $player_id ])
->select('level')
->one() : null;
}
public function fields()
{
$fields = parent::fields();
if (!empty(Yii::$app->request->queryParams['player_id'])) {
$fields['_shared'] = 'sharedData';
}
return $fields;
}
a request like GET /players/9/skills or GET /players/9/skills/2 will also output the related data between both models that is stored in the related junction table:, (*27)
GET /players/9/skills/2
# outputs:
{
"id": 2,
"name": "dribble",
"_shared": {
"level": 11
}
}
Wallogit.com
