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
I've been working with external events in a resource-based calendar and had trouble retrieving the resourceId when dropping an external event using the onDropFromOutside event handler.
I came across this comment by @MALIK-0 in issue #1090 that mentions passing a resource argument, which corresponds to the resourceId. However, this isn't officially documented, which made it difficult to figure out.
Since I couldn't find much information for this use case (external events and resource-based calendar), it would be helpful to include documentation about handling resourceId within onDropFromOutside. I believe this would be beneficial for future users, especially since it’s been challenging (at least for me) to find open-source libraries that support resource scheduling effectively.
Here’s an example of how I managed to get it working:
Hi everyone!
I've been working with external events in a resource-based calendar and had trouble retrieving the
resourceId
when dropping an external event using theonDropFromOutside
event handler.I came across this comment by @MALIK-0 in issue #1090 that mentions passing a
resource
argument, which corresponds to theresourceId
. However, this isn't officially documented, which made it difficult to figure out.Since I couldn't find much information for this use case (external events and resource-based calendar), it would be helpful to include documentation about handling
resourceId
withinonDropFromOutside
. I believe this would be beneficial for future users, especially since it’s been challenging (at least for me) to find open-source libraries that support resource scheduling effectively.Here’s an example of how I managed to get it working:
Thank you very much for the awesome work!! This library has been a lifesaver for my project.
The text was updated successfully, but these errors were encountered: