form-extraction

Extracting Angular Reactive Forms involves scanning TypeScript and HTML files to identify formControlName, formGroupName, and FormBuilder definitions. This identifies controls, validators, and their definitions for migration comparison and validation logic analysis.

Mapping old Angular Validators to OneValidators involves detecting both validator types in TypeScript files. The extraction process identifies built-in Validators, new OneValidators, and custom validators, generating a clear mapping from old syntax to new OneValidators syntax.

Auditing form controls during Angular migration involves extracting all formControlName and formGroupName instances from HTML and form definitions from TypeScript. This ensures consistency and prevents runtime errors by comparing legacy and migrated codebases.

Yes, you can extract custom validators and form group validation logic from TypeScript files. The extraction process detects OneValidators, custom validators, and form group and control-level validation logic to support detailed analysis and migration comparison.

The best way to display Angular validation errors is to differentiate between built-in messages and custom handling in templates. The extraction process guides correct error display patterns by analyzing validation logic from form controls and validators.

Yes, the form-extraction skill compares form controls between legacy and migrated Angular codebases. It extracts controls, validators, and definitions from TypeScript and HTML files to facilitate migration comparison and ensure consistency across the application.