certain EventApi prop getters (like startEditable) be computed?

When defining the options object when creating a calendar, the property eventStartEditable is ignored. You need to manually set startEditable for each Event to drag them around.

[baileyandy]

Confirmed. I was about to raise this myself (see comment end for workaround). My use-case might be different as I am setting editable on the EventSource - although setting startEditable on the EventSource does not seem to work either.

If I understand correctly, the EventApi exposes editable as startEditable and durationEditable but when I try to use startEditable in an eventOverlap function, for example:

this.fullCalendar = new FullCalendar.Calendar(this.calendarRef, {
    eventOverlap: this.eventOverlap,
});

this.fullCalendar.addEventSource({
    rendering: 'background',
    editable: false
    events: getFn
});

private eventOverlap(stillEvent: EventApi, movingEvent: EventApi) {
    return !stillEvent.startEditable && movingEvent.startEditable;
}

it is always null, as are all the props exposed from the def object.

This seems to be a regression since v4-alpha.1

As a workaround, I can access the correct value via stillEvent.source.internalEventSource.startEditable

[chuchiperriman]

Same problem here. We return a list of events some editable: true and others with editable: false. In the eventClick I’m trying to access eventClickInfo.event.editable but the the property does not exists.

I’m searching for a workaround in fullcalendar 5 while these properties are added

Fixed using eventClickInfo.event.startEditable instead of editable.