Refactor forms to use final-form instead of redux-form

Description

Many components use redux-form:

In an ideal world, we would issue a breaking change and import Field, FieldArray etc from `final-form` but in order to do this in a non-breaking way, we can refactor them to accept props like fieldClass, fieldArrayClass, etc. in order to allow the calling components to override the (default: redux-form) class that is instantiated.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Khalilah Gambrell July 16, 2020 at 1:15 PM

Created smaller tasks

Zak Burke February 12, 2020 at 6:50 PM

Track it as whatever type is fits best, and yes, assign the related tickets to the app owners/teams.

Khalilah Gambrell February 12, 2020 at 5:42 PM

- Refactor forms to use-final form be tracked as a Feature? And should each task be assigned to applicable app owners?

Duplicate

Details

Assignee

Reporter

Priority

Sprint

Development Team

Spitfire

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created February 7, 2020 at 3:47 PM
Updated October 9, 2020 at 5:49 PM
Resolved July 16, 2020 at 1:15 PM
TestRail: Cases
TestRail: Runs