Difficult to subclass views for creating custom views

[arshaw]

As @benvan points out in #3357, if you want to subclass a standard view, you also need to port over it's defaults as well. Otherwise, in agendaview at least, slotDuration will be null and there will be an infinite loop. Workaround:

var agendaViewMeta = FC.views.agenda;
var AgendaView = agendaViewMeta['class'];

FC.views.myCustomView = {
  class: AgendaView.extend({ }),
  defaults: agendaViewMeta.defaults
}

It'd be nicer to bake in the options closer to the class. So, in agenda/config.js for example:

AgendaView.defaults = {
	allDaySlot: true,
	slotDuration: '00:30:00',
	slotEventOverlap: true // a bad name. confused with overlap/constraint system	
};

fcViews.customView = AgendaView.extendWithDefaults({ // or something like this
	duration: { days: 1 }
});

Which would allow for something like this:

fcViews.myCustomView = FC.AgendaView.extendWithOptions({
	// more defaults
});

[arshaw]

This issue has been addressed in the latest alpha release (4.0.0-alpha.2)
See the blog post »

This has gotten better:
https://fullcalendar.io/docs/v4/release-notes#view-api

but still might change a bit

[arshaw]

I'm closing this issue to signify that it's implemented (since v4-alpha2). I'll comment on this thread again when v4 is officially released, or if there are further API changes with this.

[arshaw]

V4 was officially released a few days ago!

Simply subclassing a view is all that's required. All options directed at the base view will automatically be applied to the subclass views, without requiring any hacks.