Skip to content

Defining global patterns before parent boot function call #3338

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
Apr 11, 2015

Conversation

makque
Copy link

@makque makque commented Apr 10, 2015

Kindly check if my assumption is correct? In relation to this issue, http://stackoverflow.com/questions/28251154/laravel-5-0-dev-defining-global-patterns-is-not-working/29567578#29567578 and https://laracasts.com/discuss/channels/general-discussion/route-global-pattern-in-routeserviceprovider-not-working-in-laravel-5?page=1

Not really an issue, it's just probably creating some confusions for others

or this could be a different issue/bug

thanks!

taylorotwell added a commit that referenced this pull request Apr 11, 2015
Defining global patterns before parent boot function call
@taylorotwell taylorotwell merged commit a9a59c1 into laravel:master Apr 11, 2015
//

parent::boot($router);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what does this commit change ?

It's almost the same code with an useless comment strip and a new empty line. I don't see the relation between this and the pull request description.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comment strip is where the dev should put his code.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was not obvious... thank you for your answer @RomainLanz :)

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.

4 participants