Orders Table: Filtering and Ordering

Hello, I have a question for this function:

	public function deleteSelected(): void
	{
	
			$orders = Order::whereIn('id', $this->selected)->get();

			$orders->each->delete();

			$this->reset('selected');
	}
	

why in this function we loop over the orders then delete them instead of deleting them directly like this:

	Order::whereIn('id', $this->selected)->delete();

As I know that deleting them directly has better performance right? Correct me if I'm wrong please.

Thanks.

I have been experimenting with two aspects of this tutorial, and I Have created a need for something outside the scope but I still want to learn how to do it! We select can select multiple items, and then delete them. I would like to pass an array of names of each item to sweet alert, so that the user can stop the delete if they see something in the displayed list of what is about to be deleted in case they realize that is wrong. I tried a couple of things for this, I was able to adjust the code for a single delete, and pass the name of individual item to sweet alert. I think I need to build an array of these selected names, and pass them to the alert. does this logic exist elsewhere? does this make sense as a feature / concept?

TailwindCSS overrides some styles of Pikaday, you must put pikaday styles after @vite([ ... ])

@vite(['resources/css/app.css', 'resources/js/app.js'])
<link href="https://cdn.jsdelivr.net/npm/pikaday/css/pikaday.css" rel="stylesheet">

What about query strings with the filters?

the blade file includes another "svg.sort", in which part of this course is that created?

In order to make delete selected button to be able to be activated when orders are checked, change

<input type="checkbox" value="{{ $order->id }}" wire:model="selected">

to

<input type="checkbox" value="{{ $order->id }}" wire:model.live="selected">