All notable changes to this project will be documented in this file. See commit-and-tag-version for commit guidelines.
13.0.0 (2024-12-06)
- ngx-valdemort is now based on Angular 19.x. If you want to use it with an older version of Angular, then stick to a previous version of ngx-valdemort.
- use control flow syntax in readme example (6499798)
12.0.0 (2024-05-26)
ngx-valdemortis now based on Angular 18.x. If you want to use it with an older version of Angular, then stick to a previous version ofngx-valdemort.
11.0.0 (2023-11-15)
ngx-valdemortis now based on Angular 17.x. If you want to use it with an older version of Angular, then stick to a previous version ofngx-valdemort.
10.0.1 (2023-05-05)
- fix dependency version in published package.json (8c50d05)
10.0.0 (2023-05-05)
ngx-valdemortis now based on Angular 16.x. If you want to use it with an older version of Angular, then stick to a previous version ofngx-valdemort.
9.0.0 (2022-11-18)
All components and directives are now standalone. The ValdemortModule is still usable as it was before,
but you can also import the directives directly, from your standalone components or from your modules.
We have also updated our documentation about the integration of ngx-valdemort in Angular Material applications, because a tiny CSS adjustment is now necessary for error messages to look good with material.
ngx-valdemortis now based on Angular 15.x. If you want to use it with an older version of Angular, then stick to a previous version ofngx-valdemort.
8.1.0 (2022-10-08)
- improve typing of the structural directives (34ddd5b)
8.0.0 (2022-06-03)
ngx-valdemortis now based on Angular 14.x. If you want to use it with an older version of Angular, then stick to the previous version ofngx-valdemort.
7.0.0 (2021-11-04)
ngx-valdemortis now based on Angular 13.x. It also needs RxJS v7.4+. If you want to use it with an older version of Angular, then stick to the previous version ofngx-valdemort.
-
angular config invalid tsconfig reference (0921257)
-
remove debug expression from demo (0502df0)
-
migrate to ng and cli v13 (2fa7cb0)
6.0.0 (2021-05-13)
- ngx-valdemort now targets Angular 12.0.0 and Ivy only. If you want to use it with Angular 11.x or View Engine, stick to the previous version of ngx-valdemort. Partial Ivy compilation is now enabled, allowing ngcc to skip this package and you to have faster builds! 🚀
- enable Ivy partial compilation (5166464)
- renovate config (80edb78)
5.1.0 (2021-04-09)
The template of the valFallback directive is used for all the errors that exist on the form control but are not handled by any of the specific error templates:
<val-default-errors>
<ng-template valError="required" let-label>{{ label }} is mandatory</ng-template>
<ng-template valError="max" let-error="error" let-label>{{ label }} must be at most {{ error.max | number }}</ng-template>
<ng-template valFallback let-label let-type="type" let-error="error"
>{{ label }} has an unhandled error of type {{ type }}: {{ error | json }}</ng-template
>
</val-default-errors>- allow throwing on missing control (c2b739b)
This adds a configuration option called shouldThrowOnMissingControl that checks if the control is not found, if set to a function that returns true.
It is set to a function that returns false by default, so this is not breaking change.
This allows to catch situations where the controlName has been wrongly specified:
<input id="firstName" name="firstName" [(ngModel)]="user.firstName" #firstNameCtrl="ngModel" required />
<!-- the control name mentions lastName whereas the control is firstName -->
<val-errors controlName="lastName" id="firstNameErrors"></val-errors>In that case, if the new option is enabled, valdemort will throw:
ngx-valdemort: no control found for controlName: 'lastName'.
As the option accepts a function, it can easily be enabled in dev and tests, but disabled in production:
config.shouldThrowOnMissingControl = () => !environment.production;
5.1.0-beta.1 (2021-04-03)
5.1.0-beta.0 (2021-03-26)
- allow throwing on missing control (c2b739b)
This adds a configuration option called shouldThrowOnMissingControl that checks if the control is not found, if set to a function that returns true.
It is set to a function that returns false by default, so this is not breaking change.
This allows to catch situations where the controlName has been wrongly specified:
<input id="firstName" name="firstName" [(ngModel)]="user.firstName" #firstNameCtrl="ngModel" required />
<!-- the control name mentions lastName whereas the control is firstName -->
<val-errors controlName="lastName" id="firstNameErrors"></val-errors>In that case, if the new option is enabled, valdemort will throw:
ngx-valdemort: no control found for controlName: 'lastName'.
As the option accepts a function, it can easily be enabled in dev and tests, but disabled in production:
config.shouldThrowOnMissingControl = () => !environment.production;
5.0.0 (2020-11-20)
- update to Angular v11 (750d7ef)
ngx-valdemortis now based on Angular 11.x. If you want to use it with an older version of Angular, then stick to the previous version ofngx-valdemort.
4.0.0 (2020-06-26)
- update to Angular v10 (61c624b)
ngx-valdemortis now based on Angular 10.x. If you want to use it with an older version of Angular, then stick to the previous version ofngx-valdemort.
3.0.0 (2020-02-07)
ngx-valdemortis now based on Angular 9.x. If you want to use it with an older version of Angular, then stick to the previous version ofngx-valdemort.
- support basic ng-add (ac16e33)
2.0.0 (2019-05-31)
- codelyzer rule name (2474ea5)
- correct class in bootstrap integration doc (2164b97)
- fix prism highlight signature (b33bcff)
- bump to ng 8.0.0 (c5e4177)
ngx-valdemortis now based on Angular 8.x. If you want to use it with an older version of Angular, then stick to the previous version ofngx-valdemort.
1.0.0 (2018-11-02)
This 1.0.0 version is based and tested on Angular 7, although it should run fine with Angular 6. Future versions are not guaranteed to support Angular 6, though. We encourage you to upgrade.
0.1.1 (2018-09-07)
First release 🍾