Skip to content

Releases: data-driven-forms/react-forms

v3.21.10

06 Nov 14:35
Compare
Choose a tag to compare

3.21.10 (2023-11-06)

Bug fixes

@data-driven-forms/react-form-renderer~3.21.10

  • fix(renderer): pass field property to when in sequence and not

v3.21.9

06 Nov 07:56
Compare
Choose a tag to compare

3.21.9 (2023-11-06)

Bug fixes

@data-driven-forms/mui-component-mapper~3.21.9

  • fix(mui): Correctly use onBlur and onFocus for MUIDatePicker and MUITimepicker

v3.21.8

24 Oct 07:51
Compare
Choose a tag to compare

3.21.8 (2023-10-24)

Bug fixes

@data-driven-forms/pf4-component-mapper~3.21.8

  • fix(pf): bug in wizard navbar

The wizard navigation should only contain one WizardNav component. Wrapping the WizardNavItems
in two WizardNav components is causing all steps to be treated as substeps and therefore don't
have step numbers. The fix is to remove one of the WizardNav wrappers.

v3.21.7

16 Oct 12:54
Compare
Choose a tag to compare

3.21.7 (2023-10-16)

Bug fixes

@data-driven-forms/pf4-component-mapper~3.21.7

  • fix(pf4): fix bug in wizard navigation toolbar

In Patternfly 4, the WizardNavItem component step prop is "the step
passed into the onNavItemClick callback".

http://v4-archive.patternfly.org/v4/components/wizard#wizardnavitem

In Patternfly 5, onNavItemClick no longer exists. Instead, there is an
onClick callback which expects the index of the step to be navigated to.

https://www.patternfly.org/components/wizard/#wizardnavitem

However, filtering the navSchema like so: .filter((field) => field.primary) results in substeps with field.primary===false being
dropped. Practically, this means the 2nd substep and those following it.
Therefore, the index provided by .map((step, ind) => ... is incorrect.

The correct index can still be found from step.index.

v3.21.6

18 Sep 13:31
Compare
Choose a tag to compare

3.21.6 (2023-09-18)

Bug fixes

@data-driven-forms/common~3.21.6

  • fix(common): Allow comparing select option value non primitives

@data-driven-forms/pf4-component-mapper~3.21.6

  • fix(common): Allow comparing select option value non primitives

@data-driven-forms/react-renderer-demo~3.21.6

  • fix(common): Allow comparing select option value non primitives

v3.21.5

14 Sep 09:34
Compare
Choose a tag to compare

3.21.5 (2023-09-14)

Bug fixes

@data-driven-forms/mui-component-mapper~3.21.5

  • fix(mui): Move date pickers to peer dependencies.

Resolves issues with duplicate dependencies on yarn and relaxes the
restriction of the package version.

Fixes: #1409

v3.21.4

04 Sep 07:02
Compare
Choose a tag to compare

3.21.4 (2023-09-04)

Bug fixes

@data-driven-forms/react-form-renderer~3.21.4

  • fix(renderer): remove duplicated file

v3.21.3

31 Aug 07:12
Compare
Choose a tag to compare

3.21.3 (2023-08-31)

Bug fixes

@data-driven-forms/pf4-component-mapper~3.21.3

  • fix(pf4): clean up errors and functional issues noticed on pf demo page

v3.21.2

29 Aug 11:02
Compare
Choose a tag to compare

3.21.2 (2023-08-29)

Bug fixes

@data-driven-forms/pf4-component-mapper~3.21.2

  • fix(pf4): use form classname of inModal wizard

v3.21.1

29 Aug 06:38
Compare
Choose a tag to compare

3.21.1 (2023-08-29)

Bug fixes

@data-driven-forms/pf4-component-mapper~3.21.1

  • fix(pf4): Add modal form class for PF4 wizard.

@data-driven-forms/react-renderer-demo~3.21.1

  • Fix mui date picker and time picker examples

specify stackblitz dependency on @mui/x-date-pickers for latest release of major version 5 instead of using latest which used incompatible version 6