@Alexis Thanks. But how to get it filled? When I change the view, the workdlow is triggered but the event {} object stays empty.
What do you mean with: template is empty but real event should be filled?
According to vuecal docs the following is stated:
The emitted events ready & view-change return an object:
{
view: [String],
startDate: [Date], // View start - JS native Date object.
endDate: [Date], // View end - JS native Date object.
firstCellDate: [Date], // Month view only, in case cell is out of current month - JS native Date object.
lastCellDate: [Date], // Month view only, in case cell is out of current month - JS native Date object.
outOfScopeEvents: [Array], // Month view only, all the events that are out of the current month.
events: [Array], // All the events in the current view.
week: [Integer] // Week number. Only returned if view is 'week'.
}
Note that on a month view, the events from the out of scope days (cells before and after the current month) are also returned in the array.
I checked if startDate/endDate/firstCellDate/ have a value after view change, when I change view (month/week/day) or viewed month/week/day. But it stays null.
I would expect first/last celldate should be filled, to be used in a Xano events collection. So that in Xano I only fetch events with a start_fate >= firstCellDate or startDate and end_date <= lastCellDate/endDate.
From the variables section I only have:
Furthermore I noticed that onEventClick does something with the event {} object. Here you can see that now I do have a specific view:
On CellClick I get a value in the dateISO
But current view is empty
It looks like something is nog constent in the object returned on the different emitted events. Is this something you can fix in te calendar component, on short notice? Because currently the calendar component lacks some features we need.