What if you didnt?

Not using any ajax

Can u please elaborate

https://laravel.com/docs/8.x/requests#old-input

<textarea name=”description” id=”description” type=”text”> {{old(‘description’) }}</textarea>

not working for this

show me the validation code

That’s the way to do it, fro creation at least.

$validator = Validator::make($request->all(), [
‘title’ => ‘required|string|regex:/^[a-zA-Z0-9 ]*$/|max:150’,
‘description’ => ‘required|string|max:250’,
]);

if ($validator->fails()) {

return redirect(‘release_notes/create’)->withErrors($validator)->withInput();
}

Description field

remove withErrors method

and tell me if it works

and if not above the validator declration

put $request->flash();

and edit

Nope, for edit you also have to check the value of the model.

how to live my laravel project

Nope, it should be what i last entered

Dude, it need to check what have the model and what was the input, not in that order.

oh i thought you meant the redirecting of request back to the form

Nope, i am talkin about the input, the way it is build.

That’s what was show at the moment, and is right, for creation only.

<textarea name=”description” id=”description” type=”text”> {{isset(old(‘description’)) ? old(‘description’) : $model->description}}</textarea>

this is what i mean

The user should have access to the last thing he wrote regardless of create/edit

And i didn’t say the contrary.

Just that if you make a input for only creation, the first example was more than enough.

I guess you don’t get error in a create form using $model->attribute.

I misunderstood

No problem, and a free tip

old(‘description’,$model->description)

and $model->description ?? ”

oh i didnt know that one

Old check if it exist, and accept a second parameter as a default value.

That’s what i do for my form, and i use the same form for create and edit, the only thing that change is the form action url.

depending on how you update, i think you dont have to change the url even

but thats a discussion for another day xD

Well, you have to change the method, and if we are talking about following rest routes, them you need to change the route.

what if you didnt?

public function store(){
$model = $request->the_id ? $model:findorfail($request->the_id) : new Model;
}

this will be wrong if you have an update process that is not the same as your create process

But i do follow rest route, anything can be done in another way, you can make a delete action using get, you should? of course not.

And remeber that you have to take into account that there is a user out there, that could easily change any value or add any field into a form.

heck, you could make all the logic inside the form using isset($_POST )

I understand, but i like to cut corners whenever i can

For me is better following standard names, i was really happy when i learned about restfull routes and standard name for files, like, now i don’t spend hours thinking and remembering the name of the file for user creation

Putting everything inside the same method don’t make it better, easier or shorter.

When you create a user, the email need to be unique, when you edit it, it need to be unique but taking into account the user under edit, now, if you put it in the same place you need to put extra logic to know if is creation or edition (Just giving a simple example)

But in any case, is more about perspective than good and bad, i did my years of experimenting and i stay with what worked while trying new things.

I think the best practice as you said is keeping convention. Its not like nobody else thought of merging routes before. I use at my own risk.

Yeah, i do also think so, but didn’t wanted to keep the topic, i got work that i need to finish XD.

whats amazing is how i find the time for this discussions.

https://youtu.be/P0szX_aDwR8