All Versions
82
Latest Version
Avg Release Cycle
33 days
Latest Release
142 days ago

Changelog History
Page 4

  • v6.1.1

    September 27, 2017
    • ➕ Added: React 16 as peer dependency (#498 by brycehill)
    • 👍 Allow node consumers to remove propTypes for production builds (#463 by oigewan)

    🐛 Bug fixes

    • 🛠 Fixed: disabled interaction in RTL (#471 by edoshor)

  • v6.1.0

    July 09, 2017

    👌 Improvements

    🐛 Bug fixes

    • 🛠 Fixed: before/after modifier not working as expected (#451)
    • 🛠 Fixed: changing some props would not update day cells (#452 by oigewan)
    • 🛠 Fixed: classNames may prevent clicking on outside days (#449)

  • v6.0.5

    July 02, 2017

    🐛 Bug fixes

    • 🛠 Fixed: today button inside a form submits the form (#443)
    • 🛠 Fixed: before/after modifiers not working as expected in some cases (#442)
    • 🛠 DayPickerInput Fixed: allow multiple formats in format prop (#439)

  • v6.0.4

    June 26, 2017

    🐛 Bug fixes

    • 🛠 Fixed: next and previous buttons not working via keyboard (#430)
    • 🛠 Fixed: wrapper style cannot be set when using CSS modules (#432)

  • v6.0.3

    June 22, 2017

    🐛 Bug fixes

    • DayPickerInput Call onDayChange(undefined, {}) when user empties the input field. (#423)
    • ⚡️ DayPickerInput Fixed: shown month was not updated when updating month in dayPickerProps (#425)

  • v6.0.0

    June 16, 2017

    🚀 This major release focuses on performance, improves accessibility and fixes some 🐛 bugs. There are some possible breaking changes, but they are easy to fix (read below).

    💥 Breaking changes

    • The container's HTML structure has changed: the interactive element used to focus the calendar has been moved into a wrapper to improve accessibility (#392):
      <div className="DayPicker">
  + <div className="DayPicker-wrapper">
    <!-- rendered stuff here -->
  + </div>
  </div>

    This is a breaking change if you are styling the component using your own CSS or with the classNames prop.

    • If you are styling with your own stylesheet, rename your .DayPicker selector to .DayPicker-wrapper:
      - .DayPicker {
  + .DayPicker-wrapper {

    • If you are using classNames with the container prop, rename the container className to wrapper.

      • The container element is now an inline-block element.
      • When using fromMonth/toMonth props, navigation buttons now are rendered and hidden via CSS. Before, the buttons were not rendered at all, and it was impossible to style them (#366)

    This is a breaking change if you are using those props and styling the component using your own CSS or with the classNames prop.

    In such cases, the buttons will be always shown even if the previous or the next months are not navigable.

    • If you are styling with your own stylesheet, add a .DayPicker-NavButton--interactionDisabled selector to your style with display: none.

    • If you are using classNames, add a navButtonInteractionDisabled to your classNames with display: none to hide the buttons.

      • 👌 Improved rendering performance using shouldComponentUpdate and PureComponent (#389)

    It should not be a breaking change, but if something is not working for you when updating some props please file an issue 🙃

    👌 Improvements

    • 👍 Allow {after, before} modifiers in the same object (#354). You can now write before/after modifiers such as disabledDays={ { before: aDate, after: aDate }}.
    • DayPickerInput: added clickUnselectsDay prop to unselect and clear the input when clicking on a previously selected day (#399)

    🐛 Bug fixes

    • 🛠 Fixed an issue where users were able to focus outside days (#400 by oigewan)
    • 🛠 Fixed an issue with Internet Explorer 11 (#403 by oigewan)
    • a11y: fixed a warning You have an unlabeled element or control. shown with react-a11y (#386)
    • DayPickerInput: fixed an issue when updating the month's dayPickerProps value (#380 by Yustynn)

    👌 Improvements in the built version

    🏗 These changes applies to the production build from the lib dir (e.g. that served from unpkg.com).

    • ✂ Removed prop types from production build (#349)
    • Include DayPicker.Input in the built file (#383)

    Use <DayPicker.Input /> to render the input component.

  • v5.5.3

    May 25, 2017
    • 🛠 Bugfix for DayPickerInput: updated value prop now will be reflected in the component's state (#363)

  • v5.5.0

    May 09, 2017

    🆕 New DayPickerInput component

    👉 Use the DayPickerInput component to render an input field interacting with the day picker (#213).

    👀 See example, 📄 docs and 📄 API reference.

    🆕 New features

    Use this prop to display a button on the calendar's footer to switch to the current month (example).

    Use this props to display and interact with the year's week numbers (example).

    For example, to match Sundays and Mondays:

      <DayPicker
    disabledDays={
  -    day => day.getDate() === 0 || day.getDate() === 1
  +    daysOfWeek: [0, 1]
    }
  />

  • v5.4.3

    May 06, 2017
    • 🛠 Bugfix: isBeforeDay/isAfterDay functions where not exported correctly (#327)

  • v5.4.2

    May 03, 2017