Same

The Same rule cross-checks a field against another named field on the same form and fails validation unless the two values match exactly — the direct opposite of the Different rule. It's the general-purpose version of the pattern the Confirmed rule automates for passwords, useful whenever two independent inputs need to agree, such as a 'repeat email' field matching the original email, or a manually retyped account number matching the one entered above it. Use the Confirmed rule instead when the pairing already follows the standard field-plus-_confirmation naming convention and doesn't need an explicit target field named.

#Directive Code Snippet

<!DOCTYPE html> 
<html lang="en"> 
    ...
    <form (ngSubmit)="onSubmit(form)" #form="ngForm">
		<input same="<TARGET_FIELD>" type="text" name="<name>" [(ngModel)]="<name>" #<name>="ngModel">
        <ng-absolute-validator [formInstance]="<name>"></ng-absolute-validator>
	</form>
    ...
</html>

#Chain Rule Code Snippet

<!DOCTYPE html> 
<html lang="en"> 
    ...
    <form (ngSubmit)="onSubmit(form)" #form="ngForm">
		<input rule="same:<TARGET_FIELD>" type="text" name="<name>" [(ngModel)]="<name>" #<name>="ngModel">
        <ng-absolute-validator [formInstance]="<name>"></ng-absolute-validator>
	</form>
    ...
</html>

#Reactive Form Code Snippet

//component.ts 
export class ReactiveComponent{

	public form  !: FormGroup;

  	constructor(
      	private fb : FormBuilder,
		private rv : ReactiveValidator,
	){this.generteForm()}

	generteForm(){
		this.form = this.fb.group({
			<name> : ['',this.rv.map('same:<TARGET_FIELD>',<CUSTOM_MESSAGE>)]
		})
	}
}

//component.html 
<!DOCTYPE html> 
<html lang="en"> 
    ...
    <form [formGroup]="form">
		<input type="text" name="<name>" formControlName="<name>">
        <ng-absolute-validator [formInstance]="form.get(<name>)"></ng-absolute-validator>
	</form>
    ...
</html>