Skip to content
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.

Fix controller namespace in event manager #171

Open
GeeH opened this issue Jun 28, 2016 · 2 comments
Open

Fix controller namespace in event manager #171

GeeH opened this issue Jun 28, 2016 · 2 comments

Comments

@GeeH
Copy link
Contributor

GeeH commented Jun 28, 2016

This issue has been moved from the zendframework repository as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html


Original Issue: https://api.github.com/repos/zendframework/zendframework/issues/7457
User: @0xPaul
Created On: 2015-04-22T09:29:40Z
Updated At: 2015-05-04T14:59:12Z
Body
Controller was only registering the root namespace, e.g. Foo instead of Foo\Bar for a class named Foo\Bar\Baz.


Comment

User: @Martin-P
Created On: 2015-04-28T19:52:56Z
Updated At: 2015-04-28T19:52:56Z
Body
Perhaps you can add:

  • a unittest which shows the correct namespace is returned
  • a separate unittest which shows the wrong namespace is not returned

That way regressions can be avoided.


Comment

User: @0xPaul
Created On: 2015-04-29T08:48:33Z
Updated At: 2015-04-29T08:48:33Z
Body
If by you, you mean someone, then yes. I'm sure someone can do those things.


Comment

User: @Martin-P
Created On: 2015-04-29T09:09:15Z
Updated At: 2015-04-29T09:09:15Z
Body

If by you, you mean someone, then yes. I'm sure someone can do those things.

I'm sure someone can create unittests, but this is not _someone_s PR, it is your PR. So I meant you, @0xPaul 😉


@internalsystemerror
Copy link

I have a Ns\SubNs\Controller\IndexController and confirm it is being picked up as Ns\SubNs... There is an undocumented feature, "view_manager" => ["controller_map" => ["Ns" => true]] which was required for the view templates to be in ns/subns/index as opposed to ns/index...

@weierophinney
Copy link
Member

This repository has been closed and moved to laminas/laminas-mvc; a new issue has been opened at laminas/laminas-mvc#29.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants