v5 component refactor: File uploader

[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 'FileInput' - DS is 'FileUploader'
• 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 Elements Audit in Figma
• Link to Elements
• Accessibility requirements - TBC

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: In my opinion, this work should be deferred for later. File uploaders are not simple to build and, while we could focus on just the presentational concerns, I think there's still a decent amount of thinking required to ensure we build those presentational atoms in a way that allows as many of our products to leverage them correctly despite a myriad of different file upload "tech stacks" and user experiences.