All language subtitles for 7. Functions of Delete API

OK, guys, welcome to the course of Lavallade Epitaph material, this is part 16 inside this video,

Violetta Volkova Delete Epper concept.

So if I go back to Ed in the last video we had worked over Update Epper and The Last Method and the

last episode we will see inside this video all about this epic Anthoula, all about delete API, let's

delete employ method.

So what I will do simply the same we to check for that on the behalf of this employee ID the employer

exists or not.

If we do exist then we will delete otherwise employee not found.

So let's say if employee will use Vehle method ID equals to ID and will use existing method.

If an employee accessed what will do simply will delete.

Otherwise, let's say employee not found.

So if I go to the Upas, like for the update here, we have the employee not found, I will copy the

same code right here inside this House floor.

It means employee not found.

And if employees accessed on behalf of this ID, it means we need to delete that SUHEIL employee equals

to employee model will use find method.

And finally, what I will do to delete this employee upset because by the help of this statement, we

are returning our employee OPSEC on the behalf of this I.T. So simply we need to delete that Employee

Jobs Act and finally we to create our response return response.

It's not resolved.

It's response.

Jaeson passing in any lets that status equals to one and message

employee deleted successfully and now save all these changes.

What we are doing here simply we are checking employee accessed or not.

If we do exist then finding the employee object and deleting here and if not accessed simply by turning

a response that is employee not found.

If I go back to post one, copy this.

You are open a new type listing util to get the UI will go to FBI dot here we have delete employee and

the request I keep in mind delete type and also we need to pass the ID means employed into the you are

going to the post man select delete request I and the EPA routley something delete hyphen employee.

So while calling this out if we pass it was the Tutty as we know that this tatties does not exist.

Click on send button employee not found.

Now suppose we want to delete this Tuddenham idea from this list from our table.

Simply past three here with a delete request I click on send button employee, delete it successfully.

Now if you go to the list, click on Send Button.

And as you can see that we have already called one, two and four.

Tuddenham Whitey is now deleted from our table.

So this is guys, how we can walk in the lateral EPWs and inside the schools successfully.

We have completed our first phase.

That is normal development without any authentication.

We have seen the overall concept, overall scenarios like creating listing, get single employed detail

updating, as well as the delete API concept.

Now from the next video, we will include our authentication tool.

Either we can include JWT, Passport or Sanctum and we will implement and see that.

How can we work with the EPA's with authentication tools and one, mooting the whole code of this first

phase.

What we have developed, I will include into the resource section of this lecture.

You can download the whole source code, what we have done here from the resource.

And also one last thing.

If I go back to post van, go here.

If I copy this, you are allowed back to Ed.

Let's include the You are Laswell.

So this is for the ad employee.

Go to Postman.

If I copied this, you are still here.

We have the you are allowed to list all the employees now next here we have the single employee detail.

Go here.

Let's say you are a single employee detail.

Next we have update employee so I will copy Goodhue.

Here we have the usual and final one we have for the delete API.

So if I will copy and paste it here.

So from the next feed, you guys will work on the second phase of development.

So for now, thank you for watching and have a great day.