Releases: data-driven-forms/react-forms
Releases · data-driven-forms/react-forms
v2.6.8
2.6.8 (2020-07-09)
Bug fixes
@data-driven-forms/pf4-component-mapper~2.6.8
- fix(pf4): allow translated strings in select
@data-driven-forms/common~2.6.8
- fix(pf4): allow translated strings in select
v2.6.7
2.6.7 (2020-07-09)
Bug fixes
@data-driven-forms/pf4-component-mapper~2.6.7
- Update tests to latest wizard changes
- fix(pf4): make wizard more translatable
- name of step is used as key
- substepOf can be now object
@data-driven-forms/react-renderer-demo~2.6.7
- Update docs to substepOf as objects
- Make babel transform plugin result's code snipet unswitchable
@data-driven-forms/common~2.6.7
- fix(pf4): make wizard more translatable
- name of step is used as key
- substepOf can be now object
@data-driven-forms/mui-component-mapper~2.6.7
- Check if demo and MUI mappers uses the same versions
- otherwise it will cause styling troubles
v2.6.6
2.6.6 (2020-07-02)
Bug fixes
@data-driven-forms/react-renderer-demo~2.6.6
- Fix demo by updating to latest MUI
@data-driven-forms/pf4-component-mapper~2.6.6
- Remove unused import in PF4 wizard types
@data-driven-forms/mui-component-mapper~2.6.6
- fix(mui): add remaining type arguments to select
@data-driven-forms/suir-component-mapper~2.6.6
- fix(suir): change datePicker to timePicker in timePicker types
v2.6.5
2.6.5 (2020-07-02)
Bug fixes
@data-driven-forms/mui-component-mapper~2.6.5
- fix(mui): replace obsolete material-ui-pickers with official package
v2.6.4
2.6.4 (2020-07-02)
Bug fixes
@data-driven-forms/react-form-renderer~2.6.4
- fix(renderer): fix wizard context types
- formOptions are defined in rendererContext
- Make dev setup more clear
- rm yarn.lock should be the last option, we should not probably encourage it as a routine
- demo repository is unclear, changet to the full name
@data-driven-forms/react-renderer-demo~2.6.4
- Get rid of duplication of text to allow searching
- Make dev setup more clear
- rm yarn.lock should be the last option, we should not probably encourage it as a routine
- demo repository is unclear, changet to the full name
- Use package title in the main component heading
- migrate docs to use firestore
- Change common headlines
- Add fallback to empty notification response
- Add spacing to nested links in docs nav
- Update other examples to include only UMD
- Update testing examples to allow module switcher
- Add bar for component mappers
- Add 404 page with redirections
- Fix links
- Add import to react form renderer component
- Added TS example to docs.
- Add env switcher to code examples
- Update field pages
- Add missing files to schema section
- Add importing section to menu
- Add constant page to schema section
- Move component examples to mappers section
- Add introduction for field schema
- Populate new documentation files
- Remove obsolete mappers file
- Move mappers to mappers section in nav
- Take URL pathname in nav, not the computed one
- Add zIndex to nav header
- Added new navigation structure to docs.
@data-driven-forms/blueprint-component-mapper~2.6.4
- Make dev setup more clear
- rm yarn.lock should be the last option, we should not probably encourage it as a routine
- demo repository is unclear, changet to the full name
- Update other examples to include only UMD
- Add bar for component mappers
@data-driven-forms/mui-component-mapper~2.6.4
- Make dev setup more clear
- rm yarn.lock should be the last option, we should not probably encourage it as a routine
- demo repository is unclear, changet to the full name
- Add bar for component mappers
@data-driven-forms/parsers~2.6.4
- Make dev setup more clear
- rm yarn.lock should be the last option, we should not probably encourage it as a routine
- demo repository is unclear, changet to the full name
@data-driven-forms/pf3-component-mapper~2.6.4
- Make dev setup more clear
- rm yarn.lock should be the last option, we should not probably encourage it as a routine
- demo repository is unclear, changet to the full name
@data-driven-forms/pf4-component-mapper~2.6.4
- Make dev setup more clear
- rm yarn.lock should be the last option, we should not probably encourage it as a routine
- demo repository is unclear, changet to the full name
- Add bar for component mappers
@data-driven-forms/suir-component-mapper~2.6.4
- Make dev setup more clear
- rm yarn.lock should be the last option, we should not probably encourage it as a routine
- demo repository is unclear, changet to the full name
- Add bar for component mappers
- Fix links
@data-driven-forms/common~2.6.4
- Fix links
v2.6.3
2.6.3 (2020-06-30)
Bug fixes
@data-driven-forms/pf4-component-mapper~2.6.3
- fix(pf4): Fix missing select pf styles
@data-driven-forms/common~2.6.3
- fix(pf4): Fix missing select pf styles
v2.6.2
2.6.2 (2020-06-29)
Bug fixes
@data-driven-forms/pf4-component-mapper~2.6.2
- fix(pf4): added disabled option to downshift select
- fix tests after pf4 select downshift migration
- replace sass loader with postcss loader for PF4
- fix(pf4): added menu portal option for downshift select
- fix(pf4): Added load options to downshift select
- fix(pf4): added multi clearable downshift select
- fix(pf4): enabled downshift multi select searchable
- fix(pf4): added multi downshift select
- fix(pf4): added searchable prop to downshift
- fix(pf4): added clearbale prop to downshift
- fix(pf4): downshift select disabled prop
- fix(pf4): replace react-select with downshift
@data-driven-forms/common~2.6.2
- fix(pf4): added disabled option to downshift select
- fix linting error after pf4 downshift migration
- replace sass loader with postcss loader for PF4
- removed unused pf4 select styled
- fix(pf4): added menu portal option for downshift select
- fix(pf4): Added load options to downshift select
- fix(pf4): added multi clearable downshift select
- fix(pf4): enabled downshift multi select searchable
- fix(pf4): added multi downshift select
- fix(pf4): added searchable prop to downshift
- fix(pf4): added clearbale prop to downshift
- fix(pf4): downshift select disabled prop
- fix(pf4): replace react-select with downshift
v2.6.1
2.6.1 (2020-06-25)
Bug fixes
@data-driven-forms/pf4-component-mapper~2.6.1
- fix(renderer): tab childs does not need component anymore
- the existence of TAB_ITEM is hidden, but it will live on until v3 is released
@data-driven-forms/react-form-renderer~2.6.1
- fix(renderer): tab childs does not need component anymore
- the existence of TAB_ITEM is hidden, but it will live on until v3 is released
@data-driven-forms/react-renderer-demo~2.6.1
- fix(renderer): tab childs does not need component anymore
- the existence of TAB_ITEM is hidden, but it will live on until v3 is released
v2.6.0
2.6.0 (2020-06-25)
Minor changes
@data-driven-forms/blueprint-component-mapper~2.6.0
- feat(common): wizard - use context to share props
- allow to set initialState
- state is being sent in onCancel and onSubmit
@data-driven-forms/common~2.6.0
- feat(common): wizard - use context to share props
- allow to set initialState
- state is being sent in onCancel and onSubmit
@data-driven-forms/mui-component-mapper~2.6.0
- feat(common): wizard - use context to share props
- allow to set initialState
- state is being sent in onCancel and onSubmit
@data-driven-forms/pf3-component-mapper~2.6.0
- feat(common): wizard - use context to share props
- allow to set initialState
- state is being sent in onCancel and onSubmit
@data-driven-forms/pf4-component-mapper~2.6.0
- feat(common): wizard - use context to share props
- allow to set initialState
- state is being sent in onCancel and onSubmit
@data-driven-forms/react-form-renderer~2.6.0
- feat(common): wizard - use context to share props
- allow to set initialState
- state is being sent in onCancel and onSubmit
@data-driven-forms/suir-component-mapper~2.6.0
- feat(common): wizard - use context to share props
- allow to set initialState
- state is being sent in onCancel and onSubmit
Bug fixes
@data-driven-forms/react-renderer-demo~2.6.0
- Update wizard docs to contain new changes
- Remove unused fonts from demo
v2.5.3
2.5.3 (2020-06-22)
Bug fixes
@data-driven-forms/react-form-renderer~2.5.3
- fix(renderer): memoize do not pass all arguments
@data-driven-forms/react-renderer-demo~2.5.3
- fix(renderer): memoize do not pass all arguments
- Use require without the context
- Compute menu in the layout
- Use common layout component for each doc page
@data-driven-forms/blueprint-component-mapper~2.5.3
- Use common layout component for each doc page
@data-driven-forms/mui-component-mapper~2.5.3
- Use common layout component for each doc page
@data-driven-forms/pf4-component-mapper~2.5.3
- Use common layout component for each doc page
@data-driven-forms/suir-component-mapper~2.5.3
- Use common layout component for each doc page