You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2023. It is now read-only.
Hi,
first many thanks for this awesome helper to integrate fullcalendar easily to svelte.
Here is my issue :
I can't modify dynamically eventData from a Draggable like I would do for other Svelte component. In others words, when I change pricedEventTitle input value, I would like the next time I drap/drop the Draggable in calendar it would take this new value as a title.
Here is a simplified code of what I have :
<script>
let pricedEventTitle = 0;
$: pricedEventData = {
title: pricedEventTitle,
};
</script>
<input bind:value={pricedEventTitle}></input>
<p>{pricedEventData.title}</p> <!-- The value is changing like expected -->
<Draggable eventData={pricedEventData}> <!-- So the object values passed is correct -->
<span>{pricedEventTitle}</span>
</Draggable>
However, as far as I understand (not sure) in Draggable.svelte, the eventData is only set at Draggable initialisation.
How would you proceed for this use case ?
Do EventData modification should propagate ?
Or may I handle manually this by destructing and recreating the Draggable at each Draggable modification ? Like this (it's working well though):
Hi,
first many thanks for this awesome helper to integrate fullcalendar easily to svelte.
Here is my issue :
I can't modify dynamically eventData from a Draggable like I would do for other Svelte component. In others words, when I change pricedEventTitle input value, I would like the next time I drap/drop the Draggable in calendar it would take this new value as a title.
Here is a simplified code of what I have :
However, as far as I understand (not sure) in
Draggable.svelte
, the eventData is only set at Draggable initialisation.How would you proceed for this use case ?
Cheers,
Valink
The text was updated successfully, but these errors were encountered: