Additional Custom Triggers #274
oldmansutton
started this conversation in
Ideas
Replies: 1 comment 1 reply
|
Current workaround involves manually finding the ok/add button for the event editor in the dom, and binding a click event listener to it, with the third argument being true, to bind to the capture phase of the event, which runs before the default click event listener for that button. Then I can do my checks, and stop propagation and prevent default to cancel the calendar's default processing. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
It would be great if there were a couple more custom triggers added (at least for my use case).
onBeforeEventAdd
onBeforeEventUpdate
I still want to use the event editor, so "onBeforeEventAddEdit" isn't an option, as that completely disables the Event Editor.
onEventAdd and onEventUpdate both happen AFTER the event is added or updated and the event editor is closed.
I require triggers before the event editor closes and actually saves the changes. In my use case, I have additional data sanity, verification and processing that needs to happen before I can accept the events as valid and finalize the save. If those criteria are not met, I need to be able to cancel out of the saving of the event.
I can likely work around this somehow as I doubt the changes will happen any time soon, if at all, but these would be a nice thing to have. Currently am trying to find a work around with a second event listener added to the confirmation button in the event editor, but since I can't guarantee in which order they fire in.....
All reactions