Skip to content
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

Multiword controller names handled properly (foo_bar now matches class FooBar) #7

Merged
merged 2 commits into from
Mar 6, 2015

Conversation

jbarket
Copy link

@jbarket jbarket commented Mar 6, 2015

When we determine the route action, we're now converting multiple_name_controller to MultipleNameController in a similar fashion to other frameworks. This is done via Laravel's camel_case followed by ucfirst since camel_case returns multipleNameController rather than MultipleNameController.

It has no effect on single word controllers, so multiplenamecontroller would still return Multiplenamecontroller like all existing code.

Jonathan Barket added 2 commits March 6, 2015 15:35
…e_controller to MultipleNameController in a similar fashion to other frameworks. This is done via Laravel's camel_case followed by ucfirst since camel_case returns multipleNameController rather than MultipleNameController.

It has no effect on single word controllers, so multiplenamecontroller would still return Multiplenamecontroller like all existing code.
joshmoody added a commit that referenced this pull request Mar 6, 2015
Multiword controller names handled properly (foo_bar now matches class FooBar)
@joshmoody joshmoody merged commit 6c10695 into werx:master Mar 6, 2015
@joshmoody
Copy link
Contributor

Looks good, thanks. Tagged as 1.11.0

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.

2 participants