Replace the instance of a file-input component in forms-system/src/js/fields/FileField.jsx with the v3 web-component #3870
Labels
bug
Something isn't working
DST-prioritized
DST PO prioritized item
forms-library
platform-design-system-team
va-file-input
Bug Report
What happened
Our component usage report turned up no instances of the v1 File input component in vets-website. However, teams keep turning up in Collab Cycle showing examples of what looks like the v1 instance of file input. That is fact this component forms-system/src/js/fields/FileField.jsx, which is an imposter.
What I expected to happen
I expected that when we had matched the functionality of the v1 file input component that we'd deprecate it in favor of the v3 component. Instead we have potentially 30 different applications all using the same lousy UX of the v1 file input.
Reproducing
You can see this FileField.jsx used in the Benefits Dependent Experience, 21-686c/674 forms and Andrew informs me that there are roughly 30 files which import the fileUploadUI which uses the FileField.jsx forms-system field.
Urgency
This is blocking our deprecation of the v1 file input user experience. While technically speaking the v1 file-input component itself isn't being used, that matters little to the user subjected to the UX, which is deficient in a number of ways.
Details
The Design System team should work with the Veteran-facing Forms team to replace the instance in the Forms system. We should first do some discovery to ensure our v3 component supports everything the FileField.jsx file offers. On that note, in future we should make a review of how a component is or is not being used in the Forms system a standard part of our component development procedure.
The text was updated successfully, but these errors were encountered: