Reusing and Fine-Tuning Desktop RESTful APIs for Mobile Apps in Yii 2.0 (Part 2)

1. The topic detail API returns the topic’s operation permissions, which include all of the current user’s permission buttons and can be customized for the mobile end (when the status is 2: Pending Review, the edit topic permission is 0: None, and the update topic permission is 0: None).

2. Edit the method file: \api\rests\plan\ViewAction.php to get the controller ID (Yii::$app->controller->id). When the route is /v1/plans/2, its value is plan, as shown in Figure 1.

3. Edit the method file: \api\rests\plan\ViewAction.php to get the controller ID (Yii::$app->controller->id). When the route is /v1/mobile/plans/2, its value is mobile/plan, as shown in Figure 2.

4. To customize for the mobile end (when the status is 2: Pending Review, the edit topic permission is 0: None, and the update topic permission is 0: None), you can evaluate the controller ID (Yii::$app->controller->id) and handle each case accordingly. Edit the method file: \api\rests\plan\ViewAction.php.

5. When the route is /v1/plans/2, both $actions[‘edit’] and $actions[‘update’] are 1, as expected, as shown in Figure 3.

6. When the route is /v1/mobile/plans/2, both $actions[‘edit’] and $actions[‘update’] are 0, as expected, as shown in Figure 4.