Releases: data-driven-forms/react-forms
Releases · data-driven-forms/react-forms
v1.28.1
1.28.1 (2020-03-04)
Bug fixes
@data-driven-forms/react-form-renderer~1.28.1
- fix(renderer): boolean is not never empty
v1.28.0
1.28.0 (2020-02-28)
Minor changes
@data-driven-forms/pf3-component-mapper~1.28.0
- feat(pf3): Input addon support for text and textarea input fields
@data-driven-forms/react-form-renderer~1.28.0
- feat(pf3): Input addon support for text and textarea input fields
v1.27.9
1.27.9 (2020-02-27)
Bug fixes
@data-driven-forms/react-form-renderer~1.27.9
- fix(renderer): add flags for pattern validator
- fix(renderer): add support for string pattern and flags
with-firebase-hosting~1.27.9
- fix(renderer): add flags for pattern validator
- fix(renderer): add support for string pattern and flags
- Add Discord link to demo
- Add fallback for releases
- GitHub's API has limit for request from one IP address
@data-driven-forms/common~1.27.9
- Add Discord link to demo
v1.27.8
1.27.8 (2020-02-24)
Bug fixes
@data-driven-forms/mui-component-mapper~1.27.8
- Use hidden instead of scss
- Add test for validation MUI tabs
- fix(mui): render all tabs into DOM
- mui: remove required from innerProps
this causes using of chrome HTML validation and that's something we doesn't want to do
v1.27.7
1.27.7 (2020-02-20)
Bug fixes
@data-driven-forms/pf4-component-mapper~1.27.7
- fix(pf4): scroll to top on switching to a different step
For instance, when there are two step that are too long for the
wizard container (e.g. too many fields) and are next to each other.
If you scroll down in one of them and switch to the other, the
location of your scroll bar won't reset to the top but will stay
at the bottom.
This is bad because the user expects the scroll bar to go back
to the top of the next step.
Signed-off-by: Boaz Shuster [email protected]
@data-driven-forms/common~1.27.7
- Add link to twitter
with-firebase-hosting~1.27.7
- Add link to twitter
- Move releases to bottom and use MUI link
- Add releases page to demo
@data-driven-forms/mui-component-mapper~1.27.7
- Limit material core to fix demo's styles
v1.27.6
1.27.6 (2020-02-10)
Bug fixes
@data-driven-forms/mui-component-mapper~1.27.6
- Add tests for MUI form fields
- Convert invalid to bool in error prop
- Update MUI select
- Show error instead of helperText
- Update MUI packages
- Fix warning in checkbox
- Fix switch
- Fix radio group
- Fix multiple checkbox
- Fix single checkbox
- Fix date and time pickers
- When empty value, use null
Timepicker/Date picker cannot handle empty strings
- Add description as a fallback to helperText
- Update sandbox for MUI to contain everything
- fix(mui): Add tests for MUI select
@data-driven-forms/common~1.27.6
- Convert invalid to bool in error prop
v1.27.5
1.27.5 (2020-02-10)
Bug fixes
@data-driven-forms/mui-component-mapper~1.27.5
- Remove key assigning in components
- Removes all mention of keys from schemas
@data-driven-forms/pf3-component-mapper~1.27.5
- Remove key assigning in components
- Removes all mention of keys from schemas
@data-driven-forms/pf4-component-mapper~1.27.5
- Remove key assigning in components
- Removes all mention of keys from schemas
@data-driven-forms/react-form-renderer~1.27.5
- Removes all mention of keys from schemas
- fix(renderer): Check if the field has name set, not title or key
with-firebase-hosting~1.27.5
- Removes all mention of keys from schemas
- Add and fix table of contents where missing
v1.27.4
1.27.4 (2020-02-05)
Bug fixes
@data-driven-forms/pf4-component-mapper~1.27.4
- fix(renderer): fix conditions for nested names
@data-driven-forms/react-form-renderer~1.27.4
- fix(renderer): fix conditions for nested names
v1.27.3
1.27.3 (2020-02-03)
Bug fixes
with-firebase-hosting~1.27.3
- Tree shake PF4 in demo
- fix(pf4): use tree shaking for PF4 dep
@data-driven-forms/pf4-component-mapper~1.27.3
- fix(pf4): use tree shaking for PF4 dep
v1.27.2
1.27.2 (2020-01-31)
Bug fixes
@data-driven-forms/pf4-component-mapper~1.27.2
- fix(pf4): Multi async select initial value change.