{"id":528,"date":"2023-02-21T05:00:00","date_gmt":"2023-02-21T13:00:00","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=528"},"modified":"2023-02-17T16:19:37","modified_gmt":"2023-02-18T00:19:37","slug":"implementing-custom-feedback-to-form-validation-with-angular","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/implementing-custom-feedback-to-form-validation-with-angular\/","title":{"rendered":"Implementing custom feedback to form validation with Angular"},"content":{"rendered":"\n<p>Yesterday, we saw that Angular uses <a href=\"https:\/\/angular.io\/guide\/form-validation#control-status-css-classes\" target=\"_blank\" rel=\"noopener\" title=\"\">six different CSS classes<\/a> (actually, eight &#8211; I didn&#8217;t mention <code>ng-pending<\/code>, which is the temporary state when async validation is being performed, and <code>ng-submitted<\/code>, which applies to the form element only). <\/p>\n\n\n\n<p>Today, let&#8217;s see how we can customize the feedback displayed to the user beyond CSS classes. The nice thing about Angular validation properties is that they&#8217;re not just available as CSS classes. They are also available as public properties on the <code>ngModel<\/code> and the <code>ngForm<\/code> directives used in our form.<\/p>\n\n\n\n<p>We can access such properties using <a href=\"https:\/\/www.angulartraining.com\/daily-newsletter\/template-reference-variables\/\" title=\"\">template reference variables<\/a> to access the <a href=\"https:\/\/www.angulartraining.com\/daily-newsletter\/exported-directives\/\" target=\"_blank\" rel=\"noopener\" title=\"\">exported values of these directives<\/a> as follows:<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"84\" src=\"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-41.png\" alt=\"\" class=\"wp-image-530\" srcset=\"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-41.png 800w, https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-41-300x32.png 300w, https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-41-768x81.png 768w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><\/figure>\n<\/div>\n\n\n<p><\/p>\n\n\n\n<p>The above code would result in the following rendering:<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"249\" height=\"55\" src=\"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-42.png\" alt=\"\" class=\"wp-image-531\"\/><\/figure>\n<\/div>\n\n\n<p><\/p>\n\n\n\n<p>Of course, displaying <code>true<\/code> or <code>false<\/code> is not very user-friendly. Instead, we can use *ngIf and make the experience a little more polished:<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"799\" height=\"127\" src=\"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-43.png\" alt=\"\" class=\"wp-image-532\" srcset=\"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-43.png 799w, https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-43-300x48.png 300w, https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-43-768x122.png 768w\" sizes=\"auto, (max-width: 799px) 100vw, 799px\" \/><\/figure>\n<\/div>\n\n\n<p><\/p>\n\n\n\n<p>Which looks like this:<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"266\" height=\"58\" src=\"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-44.png\" alt=\"\" class=\"wp-image-533\"\/><\/figure>\n<\/div>\n\n\n<p>We can apply the same idea to the <code>form<\/code> element and decide to disable the submit button as long as the form is invalid:<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"556\" height=\"161\" src=\"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-45.png\" alt=\"\" class=\"wp-image-535\" srcset=\"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-45.png 556w, https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-45-300x87.png 300w\" sizes=\"auto, (max-width: 556px) 100vw, 556px\" \/><\/figure>\n<\/div>\n\n\n<p><\/p>\n\n\n\n<p>Or we could even hide the button as long as the form is invalid:<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-46.png\" alt=\"\" class=\"wp-image-536\" width=\"447\" height=\"42\" srcset=\"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-46.png 447w, https:\/\/www.angulartraining.com\/daily-newsletter\/wp-content\/uploads\/2023\/02\/image-46-300x28.png 300w\" sizes=\"auto, (max-width: 447px) 100vw, 447px\" \/><\/figure>\n<\/div>\n\n\n<p><\/p>\n\n\n\n<p>You get the idea. As simple as those validation properties are, they enable many possible different customizations of how we display validation feedback and hints to the user.<\/p>\n\n\n\n<p>You can <a href=\"https:\/\/stackblitz.com\/edit\/ng-custom-feedback?file=src%2Fmain.ts,src%2Fmain.html\" target=\"_blank\" rel=\"noopener\" title=\"\">play with my code example on Stackblitz<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Yesterday, we saw that Angular uses six different CSS classes (actually, eight &#8211; I didn&#8217;t mention ng-pending, which is the temporary state when async validation is being performed, and ng-submitted, which applies to the form element only). Today, let&#8217;s see how we can customize the feedback displayed to the user beyond CSS classes. The nice [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,22],"tags":[],"class_list":["post-528","post","type-post","status-publish","format-standard","hentry","category-angular","category-forms"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-json\/wp\/v2\/posts\/528","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-json\/wp\/v2\/comments?post=528"}],"version-history":[{"count":6,"href":"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-json\/wp\/v2\/posts\/528\/revisions"}],"predecessor-version":[{"id":540,"href":"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-json\/wp\/v2\/posts\/528\/revisions\/540"}],"wp:attachment":[{"href":"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-json\/wp\/v2\/media?parent=528"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-json\/wp\/v2\/categories?post=528"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.angulartraining.com\/daily-newsletter\/wp-json\/wp\/v2\/tags?post=528"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}