[Proposal] Route::current()->parametersWithoutBind()

[raiika]

For some reason I need to get the url parameters without the bind while using bind (the url value).

Route::current()->parametersWithoutBind()

[sisve]

Could you give an example of what you want to retrieve? What is "without the bind"?

[michaeldyrynda]

I assume the string value that’s in the URL, rather than the bound model

[deleugpn]

Looks weird to me. If the string in the url was capable of mutating into an eloquent object, it knows how to go back to being a string.

[raiika]

May I know how Laravel handle it ? Or should I make it myself ?

[rs-sliske]

$model->getRouteKey() ?

[raiika]

I am using custom Route::bind

[sisve]

I still have no clue what you're asking for. Could your clarify what "get the url parameters without the bind while using bind (the url value)" means?

If you have a {locale}/zomg/{user} route, then $route->parameters will give you a keyed collection with the values.

// $route->parameters
array(
    "locale" => (the locale object),
    "user" => (the user object)
)

If you just want the url;

// $route->uri
"{locale}/zomg/{user}"

Does any of these address your problem? If not, can you clarify what you you want?

[raiika]

Rather than object, I want the string

[deleugpn]

From the request object, you may use $request->segment($index); to get the segmentation of the Path the Router loaded. Either way, I stand by my first comment. The object knows how to make up the string because it was resolved said string.

[sisve]

@raiika Are you asking about the original value that was resolved into the object? As in, if I keep my {locale}/zomg/{user} example and the url sv-se/zomg/1337, are you asking for the "1337" value instead of the User object?

@deleugpn You presume that the object is a Eloquent model and you've used implicit binding. Explicit binding can resolve things in any weird way, and there's no requirement for the object generated to even have a stringable representation.

[raiika]

@sisve yes, that's right.

[sisve]

I do not know of any way to get that information with the current api. Going via $request->segments(), as @deleugpn mentioned, is probably the quickest solution, but you may still look into the route objects different properties to figure calculate which segment you're looking for,

[raiika]

@sisve yeah, and I know this won't be implemented in the future so I guess I'll just use another way of retrieving the string. Thanks anyway for your time.

[fletch3555]

Doesn't the route model binding work based on the model's primary key? Given this, can't you get the value by doing something like:

$parameterWanted = 'user';
$value = $route->parameters[$parameterWanted]->getKey();

This uses the parameter list mentioned by @sisve above. Since you know what parameter you want, you can get the model object. Once you have a model object, you can get to the model's primary key value. This still requires the query to run, and to appropriately return a model instance, but that will need to occur anyway for the route-model binding to work. Otherwise that system would throw a 404, and the code within the controller method would never run.

An alternative is to simply not use the route-model binding. Then you'll have the ID right away. You can then use that to get the model instance manually, or throw a 404 as needed.

[rs-sliske]

@fletch3555 by default it goes off the primary key, but you can customize which field is used,

$model->getRouteKey() returns the identifier which is used for route generation.

@raiika whats your use case?
you could maybe add your own middleware to store the parameters somewhere before the model binding runs, or disable the binding on certain endpoints