Validate an encoded route key

[cybercog]

Validate an encoded route key

[ivanvermeyen]

Thanks for the input!

That's also an interesting approach. Looks cleaner than newing up the rule manually.

I've added the static constructor method model(). 👍

RouteKeyExists::model(Article::class)->replace()

[antonkomarev]

Hello, @ivanvermeyen.

Package you provided seems useful. Good to have it as separate package as you've done it.

So, it's validating if model exists using encoded key and overwriting this id in request with decoded one?

If I will execute:

$validated = validate([
    'article' => new RouteKeyExists(Article::class)->replace(),
]);

This will have actual Article id?

dd($validated['article']);

So much magic :}

[ivanvermeyen]

Indeed, but you'll need extra parentheses:

$validated = validate([
    'article' => (new RouteKeyExists(Article::class))->replace(),
]);

I was in doubt if I should add an optional second constructor parameter to enable replace or add. I think it's slightly less clear, but maybe prettier to look at without those extra parentheses? I think I will add this for flexibility...

$validated = validate([
    'article' => new RouteKeyExists(Article::class, 'article'), // store the original ID in request('article')
]);

The real logic for checking if it exists is in the models resolveRouteBinding() method, like the one in your trait, so it's not tightly coupled to a single use case. :) All I'm doing is this in essence:

if ( ! $model = $this->model->resolveRouteBinding($value)) {
    return false; // validation fails...
}

And then some checks if I should replace or add the original ID to the request.

[antonkomarev]

One more possible solution is static factory:

$validated = validate([
    'article' => RouteKeyExists::model(Article::class)->replace(),
]);

Or name it as you like: make or anything else. Or even this:

$validated = validate([
    'article' => RouteKeyExists::replace(Article::class),
]);

[antonkomarev]

Yeah, this one looks good. We could add suggestion for Laravel Optimus users to readme or composer.json that there is optional way to validate if encoded models are exists. But first of all I need to start using them myself. I've never done it in any production projects.