v0.21.0
What’s Changed
💥 Breaking changes
Migration guide
The DateField has been rewritten from scratch using react-aria, which greatly improves the accessibility, by better supporting the wide range of possible inputs (mouse, keyboard, touch, screen reader).
We introduced some subtle changes in the UI and UX of the field, to better align with the rest of Bento. These changes are breaking in the sense that there's no way to get the old UI and UX back, but we don't expect to have a disruptive impact, in practice.
From a technical stanpoint, the only breaking change is the value accepted by the DateField when type="range".
Previously, the value (and the matching onChange) would be of type [Date | null, Date | null], meaning each of the ranges could be independently null at any point, to represent a partially selected range. This transient state is now managed internally to the component, and the type of value (and the matching onChange) is now [Date, Date] | null. In other words, DateField will not accept nor return a partial range, when in "range" mode.
Again, we don't expect this to be particularly disruptive, but if this is causing unexpected troubles, let us know by opening an issue.
🐞 Bug fixes
🔧 Dependency updates
- Update dependency @testing-library/dom to v9.3.3 (#783) @renovate-bot
- Update dependency @phosphor-icons/react to v2.0.13 (#782) @renovate-bot
