Over a million developers have joined DZone.

Angular Form Validations With Redux for Multiple Routes

DZone's Guide to

Angular Form Validations With Redux for Multiple Routes

In this quick tutorial, we take a look at how to handle some weird form validation issues, with some easy workaround in Angular using TypeScript and HTML.

· Web Dev Zone
Free Resource

Learn how to build modern digital experience apps with Crafter CMS. Download this eBook now. Brought to you in partnership with Crafter Software

Many front-end applications require the extensive use of forms to allow users to enter information. Angular supports various mechanisms to handle forms, but I’ve struggled to figure out how to handle validations of data on different pages/routes. Below is a pattern I’ve used based on Redux which doesn’t leverage much of the Angular forms functionality but works very nicely for me.

Initially, I thought that my requirements would be pretty straight forward and common for single-page applications. However, there were two things which I didn’t manage to address with core Angular forms functionality.

  • Display validation errors for multiple forms on different pages (pages from a user experience perspective; technically routes) including forms that are not currently visible. In my case, I had a sidebar component with validation errors which was displayed on every page.
  • Display validation errors for forms that have not been loaded yet. This was necessary since I read an initial set of data which was used to pre-populate forms.

Angular supports two types of forms handling – template driven forms and reactive forms. Since the reactive forms provide more flexibility I started to use them. My hope was to somehow utilize the router to load all pages without showing them, in order to trigger the out of the box form validations. Unfortunately, I didn’t get this to work without a lot of flickering and weird behavior in the user interface.

A separate issue I had was the refreshing of components. Read my older blog entry My Advice: Don’t use Angular 2+ without Redux for details. Because of the refresh issues and the form validation issues, I decided to do a bigger refactoring of my code to use Redux.

I have open sourced an application which demonstrates how Redux helps to validate data for forms before forms have been loaded. The following screenshot shows a validation error of the password field and in the right column the Redux Chrome extension which displays state information.

Image title

Here is an overview of how this has been implemented. Let’s start with the HTML for the password field.

<input [value]="watsonPassword$ | async" (blur)="onBlurWatsonPassword($event)" (keyup)="onKeyUpWatsonPassword($event)" class="form-control" id="watsonPassword" />
<div *ngIf="(validationErrorsPassword$ | async)?.length > 0" class="alert alert-warning">
    {{ (validationErrorsPassword$ | async)[0].displayText }}

In the component’s Typescript file, observables are used for the value of the password field and the validation errors. With the “xxx$ | async” notation above the values are displayed in the user interface when they change.

@select(['tool', 'watsonPassword']) watsonPassword$: Observable<boolean>;
validationErrorsPassword$: Observable<ValidationError[]>;

ngOnInit(): void {
   this.skillOverviewForm = this.formBuilder.group({});
   this.validationErrorsPassword$ = this.ngRedux.select((state) => {
      let errors: ValidationError[] = [];
      state.tool.validationErrors.forEach((validationError) => {
         if (validationError.itemName == 'watsonPassword') errors.push(validationError);
      return errors;

onKeyUpWatsonPassword(event) {
   let value: string;
   let element: any;
   element = document.getElementById('watsonPassword');
   if (element) {
      value = element.value;
      this.ngRedux.dispatch({ type: ToolAction.SET_WATSON_USER_PASSWORD, payload: value });

When users change the password, the Redux reducer is invoked which sets the new value in the Redux store and triggers the validation logic.

export function toolReducer(state: Tool = INITIAL_TOOL_STATE, action: any) {
   switch (action.type) {
      case ToolAction.SET_WATSON_USER_PASSWORD:
         newTool.watsonPassword = action.payload;            
         return newTool;     
         return state;

In the Validations class, all errors are initially deleted and (re-)created if necessary.

export class Validations {
   static validate(tool: Tool) {
      tool.validationErrors = [];

   static watsonPassword(tool: Tool): void {
      let itemName: string = 'watsonPassword';
      let error: ValidationError;
      let value: string = "";
      let validatorOutput: boolean;
      let type: string;
      if (tool.watsonPassword) {
         value = tool.watsonPassword;

      validatorOutput = Validators.required(value);
      type = Validators.errorTypeRequired;
      if (validatorOutput) {
         error = new ValidationError(itemName, 'The Watson Conversation password is required.');

Check out the full sample application, Conversation Inspector for IBM Watson, for details.

Crafter is a modern CMS platform for building modern websites and content-rich digital experiences. Download this eBook now. Brought to you in partnership with Crafter Software.

web development ,angular ,redux ,forms

Published at DZone with permission of Niklas Heidloff, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}