What is wrong with this route prefix

Question

What is wrong with this route prefix

Ramiro Martínez D'Elía Aug '16

Created Aug '16	Last Reply Aug '16	Replies 3	Views 613	Votes 0

Ramiro Martínez D'Elía 4.5k

Aug '16

Hi ! I am using annotations to define routes. But i have troubles with a route for a subresource.

I need an endpoint to manage the users addresses in my REST API, so i defined the next resource:

<?php
use Phalcon\Mvc\Router\Annotations as RouterAnnotations;
/* More  ... */
$router = new RouterAnnotations(false);
$router->addResource("Addresses", "/users/{idUser:[0-9]+}/addresses");
/* More ... */

And in my AddressesController:

<?php

use Phalcon\Mvc\Controller;
use Services\Customers as CustomersService;

/**
 * @RoutePrefix("/users/{idUser:[0-9]+}/addresses")
 */
class AddressesController extends Controller {

    /**
     * @Get("/{idAddress}")
     * @param  int  $idUser    Id del usuario.
     * @param  int $isAddress Id del domicilio.
     */
    public function readAction($idUser, $idAddress) {
        var_dump($idUser, $idAddress);
    }
}

So, when i do a GET requesto to /users/10/addresses/2 Phalcon dispatch to 404 page. Any ideas ?

Wojciech Ślawski
145.0k

Accepted
answer

Aug '16

So the issue is what i wrote. Create issue on github maybe, someday maybe this will be added. You can /users as prefix for now, sorry for this.

Wojciech Ślawski · Answer 1 · 2016-08-24T16:31:42-07:00

Im not sure if routeprefixes can even accept such a syntax like having parameter or regex. can you just check for instance if changing:

/users/{idUser:[0-9]+}/addresses to /users/10/addresses

And accessing your url again works ?

Ramiro Martínez D'Elía · Answer 2 · 2016-08-24T16:33:00-07:00

Im not sure if routeprefixes can even accept such a syntax like having parameter or regex. can you just check for instance if changing:

/users/{idUser:[0-9]+}/addresses to /users/10/addresses

And accessing your url again works ?

Yes, harcoding the user id, the url works

Jonathan Aaron Steel · Answer 3 · 2016-08-25T03:54:14-07:00

You can always override this behaviour.

This is another example (Micro app).

class MicroCollection extends \Phalcon\Mvc\Micro\Collection
{
    function setHandler($handler = null, $lazy = 0x0a)
    {
        //Inject current namespace and normally proceed further treatment of request to a parent method
        return parent::{__FUNCTION__}(__NAMESPACE__ . '\\' . $handler, $lazy);
    }
}