Releases: cloudnc/ngx-sub-form
Releases · cloudnc/ngx-sub-form
v5.2.0-feat-rewrite.1
5.2.0-feat-rewrite.1 (2020-09-13)
Features
- rewrite of ngx-sub-form without inheritance (719d640), closes cloudnc/ngx-sub-form#82 cloudnc/ngx-sub-form#86 cloudnc/ngx-sub-form#93 cloudnc/ngx-sub-form#133 cloudnc/ngx-sub-form#143 cloudnc/ngx-sub-form#144 cloudnc/ngx-sub-form#149 cloudnc/ngx-sub-form#160 cloudnc/ngx-sub-form#168
- split old and new API so that we can access them with ngx-sub-form and ngx-sub-form/new to avoid making a breaking change (3db939b)
v5.1.2
v5.1.1
v5.1.0
5.1.0 (2020-02-26)
Bug Fixes
- formatting: ran prettier:write (4c9f247)
- formatting: ran yarn run prettier:write (b5e2cee)
- lint: ignore interface-over-type-literal for TypedControlBase as all others are types as well (733f5c2)
- typed-form-array: set/patchValue now use TValue directly as it extends any[] (1472ab0)
- typings: remove the use of omit to remove build errors when using Ivy #134 (f264775)
- typings: use Abstract control setValue/patchValue for TypedAbstractControl (1ff3e3f)
- typings: use Parameter<> for setValue / patchValue + refactored base typing (4d303bd)
Features
- ControlsType: added typings for AbstractControls + FormArrays (1e7d271)
- readme: updated list of interfaces (338a9b8)
- typing: added control typings for form group (f389439)
- typings: updated typings for ControlType to an intersection for non arrays (a658d31)
- typings: use optional typing for patch/setValue on TypedAbstractControl (c1afcdd)
v5.0.1
v5.0.0
5.0.0 (2020-02-19)
Features
- lib: upgrade to Angular 9 (b8890b8), closes cloudnc/ngx-sub-form#101 cloudnc/ngx-sub-form#102 cloudnc/ngx-sub-form#134
BREAKING CHANGES
- lib: requires angular 9
v4.0.1
v4.0.0
4.0.0 (2019-12-19)
Bug Fixes
- lib: remap and root form components don't have the default values passed (only a type issue) (b58e983)
BREAKING CHANGES
- lib: Adding a parameter to the
transformToFormGroup
method could be a breaking change if you're callingsuper.transformToFormGroup
. As this method is a callback for ngx-sub-form, chances are: You're not calling it and this change will probably NOT affect you. The upgrade should go smoothly. If it does affect you, it'll be caught at build time so it should be easy to find out.
v3.0.6
3.0.6 (2019-12-18)
Bug Fixes
- lib: disabled attribute is not disabling the form if initially set to false (c858bf0), closes cloudnc/ngx-sub-form#84
v3.0.5
3.0.5 (2019-12-18)
Bug Fixes
- lib: disabled attribute not working (consistently) (79d0e89), closes cloudnc/ngx-sub-form#84