Releases: data-driven-forms/react-forms
v3.22.4
3.22.4 (2024-03-21)
Bug fixes
@data-driven-forms/common~3.22.4
- fix(common): lift compare values from select promises
- fix(common): memoize initial select options value
- fix(common): useSelect rendering loop
@data-driven-forms/react-renderer-demo~3.22.4
- Fix fielprovider typo
- Update codesandbox code template
v3.22.3
3.22.3 (2024-01-24)
Bug fixes
@data-driven-forms/ant-component-mapper~3.22.3
- fix(all): replace defaultProps with inline function defaults
@data-driven-forms/blueprint-component-mapper~3.22.3
- fix(all): replace defaultProps with inline function defaults
@data-driven-forms/carbon-component-mapper~3.22.3
- fix(all): replace defaultProps with inline function defaults
@data-driven-forms/common~3.22.3
- fix(all): replace defaultProps with inline function defaults
@data-driven-forms/mui-component-mapper~3.22.3
- fix(all): replace defaultProps with inline function defaults
@data-driven-forms/pf4-component-mapper~3.22.3
- fix(all): replace defaultProps with inline function defaults
@data-driven-forms/react-form-renderer~3.22.3
- fix(all): replace defaultProps with inline function defaults
@data-driven-forms/react-renderer-demo~3.22.3
- fix(all): replace defaultProps with inline function defaults
@data-driven-forms/suir-component-mapper~3.22.3
- fix(all): replace defaultProps with inline function defaults
v3.22.2
v3.22.1
3.22.1 (2023-12-07)
Bug fixes
@data-driven-forms/react-form-renderer~3.22.1
- fix(renderer): add missing condition mapper attribute
- fix(renderer): add mapped conditions to condition triggers
@data-driven-forms/react-renderer-demo~3.22.1
- Update number value documentation example
v3.22.0
3.22.0 (2023-11-10)
Minor changes
@data-driven-forms/react-form-renderer~3.22.0
- feat(renderer): allow condition mapping for when and is
@data-driven-forms/react-renderer-demo~3.22.0
- feat(renderer): allow condition mapping for when and is
v3.21.10
v3.21.9
v3.21.8
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
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
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