v5 component refactor: Date picker/Input Date

[HollyJoyPhillips]

Abstract

As part of the v5 Elements release, each component will be reviewed and refactored to ensure best practice and design system alignment

Specification

• Is new component or existing? Existing
• Is the component being re-named? Yes - currently it's 'InputDate' - DS is 'DatePicker'
• Is the component design signed off by product and design? Yes
• Guide to component structure & documentation in storybook
• Link to DS in Figma
• Link to Design Guidelines
• Link to Elements
• Accessibility requirements
• Additional - the developer picking the ticket up should source an appropriate OSS date picker and document usage only - it should be made clear, this is not included in the bundle and should be added as a dev dependency only however, we will support a code example of how to implement it. See comments, I think the DS references an MUI version. Will require clear documentation to explain the exported date picker from the lib is the native version only.

Developer Checklist

• [ ] Styles alignment between Design System and Elements
• [ ] Check design tokens in Figma and implement CSS variable tokens if available for relevant component
• [ ] Align with accessibility standards / spec as per above
• [ ] If relevant, break down component into Styles Only and React component structures
• [ ] Ensure all variants of components are documented as appropriate
• [ ] Ensure unit test coverage is adequate for component
• [ ] Update documentation in MDX file as per guidelines
• [ ] Changelog updated to reflect a single beta version per component ideally

Release Checklist

• [ ] Approved PR merged to main
• [ ] Design & product review and feedback addressed by developer
• [ ] Beta release by product / engineering lead to next beta version

Additional Context or Information

[kurtdoherty]

suggestion: I'd recommend deferring this for later. My understanding is Design understand how much work is required to build out a "fancy" date picker and don't view it as a must have. If this is still their view, I think we should just use the native date, time and datetime-local input element types for now.

[willmcvay]

@kurtdoherty Completely agree - the "fancy" date picker looks like a MUI component and people are very welcome to use in their code but for Elements, we'll support a keep it simple native version.