Commits on May 2, 2017

1. Rearchitecture of how modifiers are maintained and updated …

   Instead of passing down an object of modifier string => modifiers functions to each CalendarDay component and expecting the CalendarDay component to take care of updating itself, we now put the burden on the top of the tree instead of on the leaves. The previous model basically ended up meaning that whenever an interaction happened on an individual day, even a hover interaction, every single CalendarDay would have to recalculate its modifiers and rerender as a result. This was, as you can imagine, really god damn slow.
   
   In this new model, the DayPickerRangeController maintains a map with the following structure:
   ```
   {
     MONTH_ISO_1: {
       DAY_ISO_1: Set(['modifer_1', 'modifier_2', ...]),
       DAY_ISO_2: Set(['modifer_1', 'modifier_2', ...]),
       ...
     },
     ...
   }
   ```
   It passes this down the tree such that each `CalendarMonth` and each `CalendarDay` only gets the information that pertains to it. This means that the updating of these modifiers is also handled at the top-level and is done in the `componentWillReceiveProps`, `onDayMouseEnter`, and `onDayMouseLeave` methods of the `DayPickerRangeController`. Fortunately, this allows us to more finely tune which days get updated and speeds up the rerendering/updating process dramatically.

   Maja Wichrowska committed May 2, 2017
   Configuration menu

   • View commit details
   • Copy full SHA for c95cbed
   • Browse repository at this point

   Copy the full SHA

   c95cbed View commit details

   Browse the repository at this point in the history