Outdated documentation, only applicable to 1.0.0 beta 5 and below. See api-platform#191
The bundle provide a default controller class implementing CRUD operations: Dunglas\ApiBundle\Controller\ResourceController.
Basically this controller class extends the default controller class of the FrameworkBundle of Symfony providing implementations
of CRUD actions. It also provides convenient methods to retrieve the Resource class associated with the current request
and to serialize entities using normalizers provided by the bundle.
When the event system is not enough, it's possible to use custom controllers.
Your custom controller should extend the ResourceController provided by this bundle.
Example of custom controller:
<?php
// src/AppBundle/Controller/CustomController.php
namespace AppBundle\Controller;
use Dunglas\ApiBundle\Controller\ResourceController;
use Symfony\Component\HttpFoundation\Request;
class CustomController extends ResourceController
{
// Customize the AppBundle:Custom:custom action
public function getAction(Request $request, $id)
{
$this->get('logger')->info('This is my custom controller.');
return parent::getAction($request, $id);
}
}Custom controllers are often used with custom operations. If you don't create a custom operation for your custom controller, you need to register yourself that controller in the Symfony routing system and it will appear in documentations.
Note that you shouldn't use @Route annotations, as this will cause bugs. The bundle auto-registers routes within Symfony2, so you don't need to use @Route annotations.
Previous chapter: Controllers
Next chapter: Using external (JSON-LD) vocabularies