-
-
Notifications
You must be signed in to change notification settings - Fork 790
Adds Route support in App->route() #239
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
Conversation
|
I'm on the fence about this approach. On the plus side it maintains some ideal configuration for the server security. On the minus side it's breaking both the The |
|
The problem is that we have to set properties such as |
|
For security reasons you cannot implement this directy on the bundle but.. 1 you can override the class, (extends)
You don't must implement that directly on a bundle becouse that is an specific situation |
|
Has there been any update on this? I think the only difference between @emersion 's pull request and the suggestion from @cboden is that the PR sort of collects what I'd have to do anyway with the public The PR is more of a convenience method in accepting a Route object instead of a path string imo. However, what's painful about manually hitting |
|
This is a real requirement and would love to see this feature. Please have a look at this related PR: #689 |
|
Looks like this PR was automatically closed when we renamed our If you think this is still relevant, please update your branch to use |
|
I have no plans to continue working on this. If someone else wants to pick this up, please feel free! |
This PR allows to provide a Route object as $path in order to be able to build more complex endpoints, such as:
(this redirects all URLs to the controller)