Activity

1. ionitron-bot

   added

   triage

   on Nov 21, 2025
2. brandyscarney

   added

   type: feature requesta new feature, enhancement, or improvementa new feature, enhancement, or improvement

   package: angular@ionic/angular package@ionic/angular package

   on Dec 19, 2025
3. ionitron-bot

   removed

   triage

   on Dec 19, 2025
4. brandyscarney

   added the

   Feature

   issue type on Dec 19, 2025
5. rdlabo commented on Jan 30, 2026

   

   rdlabo

   on Jan 30, 2026

   Contributor

   More actions

   I migrated all forms in my Ionic Angular app to Signal Forms today, and everything is working fine so far — including dirty and touched.

   

   @luisbytes Could you clarify the specific issue you’re running into? I’m happy to do more testing on my end if that helps.
6. pankajparkar commented on Feb 7, 2026

   

   pankajparkar

   on Feb 7, 2026

   More actions

   I couldn't locate any example where signal forms being used along with ionic controls using [formField] directive.
7. pankajparkar commented on Feb 7, 2026

   

   pankajparkar

   on Feb 7, 2026

   More actions

   It works with the [formField] directive!

   I successfully migrated all forms in my Ionic Angular app to Signal Forms, and everything is working seamlessly with ion-input and other Ionic components using the [formField] attribute.

   Setup:

   import { form, required, email, FormField } from '@angular/forms/signals';
   import { IonInput } from '@ionic/angular/standalone';
   
   @Component({
     imports: [IonInput, FormField],  // Import the FormField directive
     // ...
   })
   export class MyFormComponent {
     readonly formModel = signal({ name: '', email: '' });
     
     readonly myForm = form(this.formModel, (s) => {
       required(s.name);
       required(s.email);
       email(s.email);
     });
   }
   

   Template:

   <ion-input [formField]="myForm.name" placeholder="Enter name"></ion-input>
   <ion-input [formField]="myForm.email" type="email" placeholder="Enter email"></ion-input>
   

   Why it works:

   The [formField] directive from @angular/forms/signals implements the standard ControlValueAccessor pattern under the hood. Since Ionic's form components (ion-input, ion-checkbox, etc.) already implement ControlValueAccessor, they work out of the box with Signal Forms.

   The key is importing FormField from @angular/forms/signals and adding it to your component's imports array. Then you can bind directly using [formField]="formSignal.fieldName".

   Features that work:

   ✅ Two-way binding (model updates automatically)
   ✅ dirty / touched state tracking
   ✅ Validation errors accessible via myForm.fieldName().errors()
   ✅ markAsTouched() for programmatic validation display
   Hope this helps others looking for a working example!

   👍React with 👍1Reacted by Julian Scheuchenzuber
8. ShaneK commented on Feb 9, 2026

   

   ShaneK

   on Feb 9, 2026

   Member

   More actions

   @luisbytes was this able to help with your problem? Are you still having issues with signals in Angular forms?
9. ShaneK

   added

   needs: replythe issue needs a response from the userthe issue needs a response from the user

   on Feb 9, 2026
10. ionitron-bot commented on Feb 23, 2026

    

    ionitron-botBot

    on Feb 23, 2026 – with Ionitron Bot

    More actions

    Thanks for the issue! This issue is being closed due to the lack of a reply. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.

    Thank you for using Ionic!
11. ionitron-bot

    closed this as completedon Feb 23, 2026
12. ionitron-bot

    locked and limited conversation to collaborators on Feb 23, 2026