Skip to content

Route update to call aliased Controller class #2022

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 28, 2013
Merged

Route update to call aliased Controller class #2022

merged 1 commit into from
May 28, 2013

Conversation

kirkbushell
Copy link
Contributor

Encountered an issue recently where we needed to make some updates to Controller (so that we could namespace our controllers), meaning we needed to update call/resolve methods also. However, what we found is that Route never called the aliased Controller class. This patch fixes that by ensuring the aliased class "Controller" is always called, instead of the Controller class within its own namespace (which is the default setup in config/application.php).

…her than the one within its own namespace.

Signed-off-by: Kirk Bushell <torm3nt@gmail.com>
@hasokeric
Copy link

I had the same issue, +1

taylorotwell added a commit that referenced this pull request May 28, 2013
Route update to call aliased Controller class
@taylorotwell taylorotwell merged commit c7caca4 into laravel:master May 28, 2013
@kirkbushell
Copy link
Contributor Author

This appears to have been lost with the L3 package being pulled into an L3 branch on laravel/laravel?

@taylorotwell
Copy link
Member

I don't know what you're referring to?

On Jun 24, 2013, at 5:13 PM, Kirk Bushell notifications@github.com wrote:

This appears to have been lost with the L3 package being pulled into an L3 branch on laravel/laravel?


Reply to this email directly or view it on GitHub.

@kirkbushell
Copy link
Contributor Author

This change was made for L3 a month ago, but when 3.0 branch was created - it seems to have been omitted?

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

Successfully merging this pull request may close these issues.

3 participants