Migrating v3 to v4
This guide is designed to help you through the migration. If you went through it and encountered any problems - do let us know. For more information on why certain changes were made, see the
CHANGELOG.md. When migrating to v4, use the newest version. Gradual updates will take more time and won't ease this process.
Breaking API changes
AutoFields now always takes precedence over
componentproperty on a schema. This may make your
AutoFieldrender a different component when you were using both previously. If that's the case, move your schema's
componentdefinition to a
- Dropped support for
initialCountin bridges and
ListFields. Pass a model object to the form with the appropriate amount of initial items instead.
AutoFieldscomponent in all themes now renders a
React.Fragmentinstead of a
div. Explicitly render a wrapper component around if you need one.
- Removed the
AutoFieldscomponents in all themes. Use