Server-side Rendering about daykeep-calendar-quasar

[sirbeagle]

Ok, so it would make sense to add another type of event when the viewable days update - got it and agreed.

[nicholaszuccarelli]

Closing the issue. You emit events from all the buttons - legendary!

[nicholaszuccarelli]

Reopening because as far as I can tell, the events don't actually emit the start and end dates of the selected period.

[sirbeagle]

So a "beta" version of this functionality will be in v0.3.2. This actually turned out to be a bit more difficult to implement than I thought only because of the different number of configurations that are possible with the calendar. The way it works is as follows:

When a calendar element is displayed, it'll (in theory) trigger an event that looks like:

display-change-REF
  payload: Array[1]
    0: Object
      endDate: "2019-02-07",
      numDays: 3,
      startDate: "2019-02-05",
      viewType: "CalendarMultiDay",
      visible: true

If you're just using a single calendar component (say CalendarAgenda) then visible will always be true and things are fairly self-explanatory. However, if you're using the full Calendar component things get interesting. The visible variable value should show which tab is active, but other tabs will also respond to changes (at least in my experience).

When a user navigates forward / backward then two additional values will be present in the event - moveUnit (such as 'day', 'month', etc.) and moveValue (positive indicates forward, negative indicates moving backward).

I think with all these values it should be possible to craft whatever just-in-time data look-ups you need to do. But for now I'm not going to document this and continue to refine.