Hello.
It may be not clear from the doc article but commit event is not fired if you are using local store. Local store is a store without create/delete/update urls configured. In that case records are committed immediately. If you are calling commit manually, you can fire some other event, like:
And also console shows that commit method on your store is probably incorrect. Did you try to override it? If that change is unintentional, investigate where you use 'commit' name and amend.
Since I am not using the CRUD setup on the scheduler, I need to know when an event is changed, so I can re-serialize the change back up to my sql data store. So I was under the impression that attaching to the commit event would be best.
If you need to know when event was changed, there is a change event on the store which can tell you everything. Or you can just check store changes at any point of time. Or listen to beforecommit event. Smth like:
Benefit of this approach:
1. you have access to changes only, but still can access all datatset if you need
2. you know that commit was called, which is a nice entry point if you want to only work with changes
3. next time commit is called you'll have different set of changes
Or you can serilize them every time you call commit:
eventStore.commit().then(() => serializeData(eventStore.getRange()))
// or call just after, if you don't like promises. changes are applied already
// serializeData(eventStore.getRange())