Timeslots | Get Timeslots between two values | Runtime Evironment library

Since you're using Livewire, I wouldn't worry about your ajax calls. Livewire handles them very well.

Anyhow, how is $sessionForDay getting updated by Livewire? There is no direct bind to it, since you're using Alpine's x-model and not Livewire's wire:model. If you had been using a full Livewire code, I would have suggested @entangle.

Since you are using Alpine, your code is fine for it to work. Alpine has an onchange for the select, and will update the x-model value based on the selected option. You don't need the :value attribute on the option tag, and you don't need the selector on your x-data tag.

I am not sure on why you had a variable pixelsPerHour computed. The variable firstHoursLiElWidth should do the same work as per my understanding of your code. While setting the element.width you can simply multiply the firstHoursLiElWidth with the duration of your event in hours, which is computed in hoursInProject.

I have updated your javascript. You can check below -

NOTE- Please use meaningful and self explanatory variable names. I have removed unwanted variables and cleaned up the JS code. But please change the variable names.

There nothing wrong with the function in ChartTrait.php. The Problem was in the controllers. You need to return the function you call to render the view.

Well, have you measured the impact of the logging and the serialization and the call to TimeSlotIdsToClose? Also, I would start by not sending the messages one by one but by sending messages in batches:

Your object assign is not correct. If you change : to =, code will works fine.

From what I can see, productWorkingDates1 is not a list, but rather an element of a list, of type ProductWorkingDates : ProductWorkingDates productWorkingDates1 = new ProductWorkingDates();

When trying to cast from ProductWorkingDates to List, you are facing the exception you have described : (List) productWorkingDates1

What you would need is something looking like this :

Here is a solution. I modified it to be more flexible and handle any number of time blocks.

I have solved my issue. After I get my data from the API, the moment the format has been changed to the Date format, therefore the error is shown. So, I change the date format before I init the form format.

Below is my code:

So I finally resolved this by amending the code as follows: