Camelize action name

Question

Camelize action name

dimhoLt Jul '13

Created Jul '13	Last Reply Feb '15	Replies 4	Views 1872	Votes 2

dimhoLt 22.6k

Jul '13

Hello!

I've been attempting to camlize my action names according to this instruction: https://github.com/phalcon/docs/blob/master/en/reference/dispatching.rst#camelize-action-names

However, whenever I enter a hyphen instead of a camlized name, "$dispatcher->getActionName()" is always NULL. I've removed all my custom routing to make sure there's nothing I've overridden to make it so.

Example: URL: https://localhost/user/createItem $dispatcher->getActionName() = "createItem"

URL: https://localhost/user/create-item $dispatcher->getActionName() = NULL

What am I doing wrong?

I'm runnig Apache2 on Mac OSX Mountain Lion.

Thanks.

// dimhoLt

EDIT: I solved the above issue temporarily by adding the following route:


        $router->add(
            "/([a-zA-Z\-]+)/([a-zA-Z\-]+)",
            array(
                "controller" => 1,
                "action"     => 2
            )
        );

But firstly, this seems like the wrong way to do it since /controller/action is implicit, and secondly, the correct action is still not executed (action names have lower-case first characters, so I set the action name to lcfirst(\Phalcon\Text::camelize($dispatcher->getActionName())), should be correct).

Any assistance is appreciated. Thank you.

2

Phalcon
98.9k

Accepted
answer

Jul '13

You can better camelize actions in the dispatcher: https://docs.phalcon.io/en/latest/reference/dispatching.html#camelize-action-names

dimhoLt · Answer 1 · 2013-07-23T16:14:21-07:00

Yeah, that's exactly the same instruction I showed a link to... I get NULL from action names if they're not already camelized...

jelofson · Answer 2 · 2014-12-04T15:45:53-07:00

Agreed. I also get NULL for the action name when then action is hyphenated. The router won't match an action with a - in it, so there is no action to camelize. At least that's what I see in my tests.

dimhoLt · Answer 3 · 2015-01-21T06:41:20-07:00

@jelofson Apparently, if you don't actively route anything, the path https://mysite.local/my-epic/super-page will implicitly route to MyEpicController::superPageAction(). However, it appears this doesn't work in earlier versions of Phalcon, I have not delved deeper into which version, but in 1.3.4 that I'm currently using, it does work implicitly. Try to just remove your own implementation and have Phalcon handle it silently, and it should work.

jelofson · Answer 4 · 2015-02-06T14:23:12-07:00

I still am not convinced this works out-of-the-box with the default route matching. Action names with a hyphen (-) don't get matched. I just set up a vanilla project in 1.3.4 and you won't get any matching on an action with a - in it. The default route pattern for an action is: ([a-zA-Z0-9_]+)

Therefore, you can't get the $dispatcher->getActionName() to camelize.

I used https://localhost/woop/test/hello-world where woop is the base and test is the controller.

jelofson · Answer 5 · 2015-02-06T15:03:40-07:00

Here is a good explanation. https://github.com/phalcon/cphalcon/issues/284

Not sure why this isn't the default behaviour.