Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

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

Description

Background (a) redux-form has been unsupported for years (b) stuffing form-state into the redux store is bad for performance.

Reasons for moving to final-form

  • Performance issues | For example, redux causes a page to re-render when typing (https://folio-org.atlassian.net/browse/STCOM-287)

  • Redux form is no longer updated / maintained

  • We should not maintain two libraries as a number of apps have moved to final-form

Priority

Labels

Fix versions

None

Development Team

Stripes Force

Assignee

Solution Architect

Parent

None

Parent Field Value

None

Parent Status

None

has to be done before

relates to

requires

Checklist

hide

TestRail: Results

Activity

Show:

Zak Burke February 1, 2021 at 4:56 PM

A very clear demonstration of the performance problems with redux-form.

Zak Burke February 1, 2021 at 4:47 PM

Replaces

Zak Burke February 12, 2020 at 8:13 PM

Generally, apps are free to refactor to final-form. The one potential "gotcha" is if they use components from stripes-smart-components which currently is still based around redux-form. An app pulling in <EditableList> or <AddressFieldGroup> must continue to use redux-form, at least until we provide props like fieldClass, fieldArrayClass in stripes-smart-components as discussed on STSMACOM-300.

Done

Details

Reporter

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created February 12, 2020 at 7:40 PM
Updated March 28, 2024 at 6:16 PM
Resolved March 28, 2024 at 6:16 PM
TestRail: Cases
TestRail: Runs