fosrestbundle

Is there any way to set the circular reference limit in the serializer component of Symfony (not JMSSerializer) with any config or something like that? I have a REST Application with FOSRestBundle and some Entities that contain other entities which should be serialized too. But I'm running into circular reference errors. I know how to set it like this: $encoder = new JsonEncoder(); $normalizer = new ObjectNormalizer(); $normalizer->setCircularReferenceHandler(function ($object) { return $object->getName(); }); But this has to be done in more than one controller (overhead for me). I want to set

I need to support only single API format which is JSON and I don't like to {_format} in my routes. Is it possible to remove it? In your config.yml, make sure you have this configured: fos_rest: format_listener: true routing_loader: default_format: json include_format: false Hope that helps EDIT: There is an example in the FOSRestBundle Docs that shows how to use the ClassResourceInterface . The biggest difference is that you don't have to manually define your routes at all. The interface will generate your routes based on you class name and the method name. So it is very important what you

Using Symfony2 and FOSRestBundle I am attempting to implement API methods that have some number of fixed parameters defined in the route along with some optional parameters that may exist in the query string. For example: http://somesite.com/api/method/a/b http://somesite.com/api/method/c/d?x=1&y=2 According to the documentation for FOSRestBundle , ParamFetcher is the proper way to do this, using the @QueryParam annotation. However, I already have a controller defined like: use Symfony\Bundle\FrameworkBundle\Controller\Controller; use FOS\RestBundle\Controller\Annotations\Get; use FOS

I am building an API using the FOSRestBundle and am at the stage where I need to implement the handling of the creation of new entities that contain binary data. Following the methods outlined on Sending binary data along with a REST API request sending the data as multipart/form-data feels the most practical for our implementation due to the ~33% added bandwidth required for Base64. Question How can I configure the REST end point to both handle the file within the request and perform validation on the JSON encoded entity when sending the data as multipart/form-data ? When just sending the raw

I'm developing a REST api with Symfony2 + FOSRest bundle. I would like to know if there is any way for a call to the api in dev mode ( app_dev.php ) from the browser (corresponding to a Accept: text/html,application/xhtml+xml header) to display the response in the "specified format", wrapped in html with the profiler provided by symfony. It would allow to debug calls to the api directly in the browser. Edit: I don't want to debug the HTTP request but the whole process (route matching, DB queries involved, etc). That's why I want to have access to the symfony profiler. Since Symfony 2.4, the

Is anyone used put, get, post, delete annotations(https://github.com/FriendsOfSymfony/FOSRestBundle/blob/master/Controller/Annotations/) in controller. I'm trying to use it like this, but it still takes get methods. What is the purpose of those Annotations in FOSRestBundle /** * @Route("/get/{id}", defaults={"_format" = "json"}) * @Post */ public function getObject($id) { $object = $this->getService()->findById($id); return $object; } I want to share info about all annotations. @Get, @Post, @Put, @Delete, @Head, @Patch are shortcuts for @Route + @Method, instead of using them both, you can

I'm Using FOSRestBundle for my project I've configured this route to have access to different kinf of data : ``` /** * @Rest\Get("") * * @Rest\QueryParam( * name="categoriesId", * requirements="[0-9a-zA-Z\- \/_:.,\s]", * default="", * description="The categories ids." * ) * @Rest\QueryParam( * name="orderBy", * requirements="[a-zA-Z0-9]", * default="score", * description="The keyword to search for." * ) * @Rest\QueryParam( * name="order", * requirements="asc|desc", * default="desc", * description="Sort order (asc or desc)" * ) * @Rest\QueryParam( * name="limit", * requirements="\d+", * default