symfony3 / php：从api的URL检索属性

Question

For a datatable, I have to use a REST API.

My url is for example: http://localhost:8000/trial/1

In this page to make the api call I use the following:

url: "rest->{{ path('erp_interventionapi_get') }}",

I need to get the attribut id="1" to make the correct call(find by id in the database), but I don't know how to get it.

I've tried this

    /**
 * @Rest\Get("/api_i/get")
 */
public function getAction(Request $request)
{
    $id = $request->attributes->get('id');
    $em = $this->getDoctrine()->getManager();
    $trial = $em->find('ErpBundle:Trial', $id);
    return $em->getRepository('ErpBundle:Intervention')->findBy(array('trial' => $trial));
}

but I have this error message:

The identifier id is missing for a query of ErpBundle\\Entity\\Trial

The following isn't working either:

    /**
 * @Rest\Get("/api_i/get")
 */
public function getAction($id)
{
    $em = $this->getDoctrine()->getManager();
    $trial = $em->find('ErpBundle:Trial', $id);
    return $em->getRepository('ErpBundle:Intervention')->findBy(array('trial' => $trial));
}

I guess it is because it try to retrieve the id from the url /api_i/get and not from the webpage itself.

So is it possible to get the attribute from the url where I make the API call?

Excuse me if I make mistakes in my way to say things, I'm still pretty new to this :)

Thanks in advance for your help!

Answer 1

您需要在路径函数中设置id：

{{ path('erp_interventionapi_get', {id: app.request.attributes.get('id')}) }}

Answer 2

My assumption is you're passing in the Trial object (either as a list or a single one), so when you use Symfony's Twig function path() (note, this is NOT a Twig function, it comes from the Twig bundle for Symfony), you need to pass in the id:

{{ path('erp_interventionapi_get', { id: trial.id }) }}

Or, alternatively:

{% for trial in trials %}
    {{ path('erp_interventionapi_get', { id: trial.id }) }}
{% endfor %}

https://symfony.com/doc/current/templating.html#linking-to-pages

Note, if you're outputting this as JSON for a SPA or widget-based consumption, I would recommend doing that as a client-side router strategy, eg, build the route on the client with serialized data (sans embedded URL). For instance, in Backbone you would tell it how to "get" to a resource like:

this.route("trial/:id", "trial", function(id){ ... });

http://backbonejs.org/#Router