Prop type error every time I select a new day

The calendar component renders as expected, the problem is every time I select a new day, I get a lot of errors in the console.

My render function:

  render() {
    var today = new Date();
    var minDate = Number(new Date()) - (24 * 60 * 60 * 1000) * 7;

    return (
      <InfiniteCalendar
        selectedDate={today}
        minDate={minDate}
        keyboardSupport={true}
        onSelect={ date => {
          console.log("DATE", date);
        }}
      />
    );
  }

Every time I click in a new day I get a lot of errors in the console:

warning.js:36 Warning: Failed prop type: Invalid prop `shouldHeaderAnimate` of type `object` supplied to `Header`, expected `boolean`
...
warning.js:36 Warning: Failed prop type: Invalid prop `transitionEnter` of type `object` supplied to `ReactCSSTransitionGroup`, expected `boolean`
...
warning.js:36 Warning: Failed prop type: Invalid prop `transitionLeave` of type `object` supplied to `ReactCSSTransitionGroup`, expected `boolean`.
...
warning.js:36 Warning: Failed prop type: Invalid prop `enter` of type `object` supplied to `ReactCSSTransitionGroupChild`, expected `boolean`.
    in ReactCSSTransitionGroupChild (created by ReactTransitionGroup)
...
warning.js:36 Warning: Failed prop type: Invalid prop `leave` of type `object` supplied to `ReactCSSTransitionGroupChild`, expected `boolean`.
    in ReactCSSTransitionGroupChild (created by ReactTransitionGroup)

Any thoughts how to fix this?

[leafi]

Hi, please see https://github.com/toggl/react-infinite-calendar/commit/fd1740ca0d8a9bd871e0b10ca6e58f2ec020a1e0 for one possible fix and a little extra commentary.

In effect, one of the things React does related to the creation of synthetic events is it passes more than one parameter to e.g. the onClick event handler.

While the ‘second’ argument was often undefined in one specific version of React, that changed recently. This was triggering the third, optional argument passed to onDaySelect to (sometimes?) be neither null nor undefined, causing a random event-like object to be copied to shouldHeaderAnimate in the component’s state - causing the failed prop type/invalid prop error we’re experiencing here.

I don’t think this fix should result in noticeably slower code than the original… As far as I’m aware fn.bind(blah blah) results in a new result on every call, so React should see them as different every time, so using a lambda (which React can’t test equivalence on)/new inline function (in e.g. commonjs build) will mean React thinks the onClick prop on the li changed whenever the parent is rerendered - no different from before.

Thanks for the messages above - they were extremely helpful in figuring out the issue.

[xtalx]

I get this as well (the same 5 errors listed by the OP). react-addons-css-transition-group@15.4.2 react-dom@15.4.2 react-infinite-calendar@1.2.2

I noticed that the errors are only generated the first time the the InfiniteCalendar component is mounted.