v0.10.2

Updated props and fixed bug in time-picker

v0.10.0

Additions

• More theming options
• Disabled state via disabled prop
• Improved accessibility
• Smaller bundle size - 8.2kB min + gzip
• New out-of-the-box utility functions
• Tree Shaking available

Changes

• The props for DatePicker and TimePicker have changed, find the updates at
  • Date Picker
  • Time Picker
• TimePicker limits (minTime and maxTime) have been removed, developer will the responsible for validation whenever required
• Default interval in the minutes selection dropdown has been changed to 5 minutes

New Docs Website

As the usage of this library is increasing month-by-month, I decided to create a proper documentation website for the same. I decided to use nextra - a static site generator built on top of nextjs.

The new docs can be found at https://sassy-datepicker.netlify.app

v0.9.0

Change-log

• Configuration options for DatePicker like the first day of the week
• Year Picker dropdown
• Month Picker dropdown
• New and modern styling for DatePicker and TimePicker
• Performance optimisation

Breaking Changes

• Both DatePicker and TimePicker now accept value prop instead of selected prop - like other input components
• DatePicker is a controlled component, so you need to pass a working onChange function which update the state in the parent component and re-render the DatePicker

DatePicker

DatePicker with the Month Picker open

DatePicker with the Year Picker open

v0.8.0

Bug fix mentioned in #5

v0.7.0

This release includes a new component TimePicker.

It is a named export and can be used like this -

import { TimePicker } from 'sassy-datepicker';

This release includes a major refactor to the project structure, but is backward compatible with v0.6.1.

v0.6.1

Changelog

• Patch for webpack v5 support. The issue was mentioned in PR #2 by @eddiej.
• Trimming default font-family styles.
• Update README.md to include the project roadmap.

v0.6.0

Changes

• The initialDate prop has been changed to the selected prop. This was done while fixing a buggy behaviour in the datepicker, and for semantic reasons, this prop name was chosen.
• Added support for all default reactjs props.
• Improved documentation.