feat: Expose ion-input/ion-searchbar value as a signal in Angular

[JulienLecoq]

Prerequisites

• [X] I have read the Contributing Guidelines.
• [X] I agree to follow the Code of Conduct.
• [X] I have searched for existing issues that already include this feature request, without success.

Describe the Feature Request

I would like the value property of ion-input, ion-searchbar and similar components to be exposed as signals instead of raw values. This would allow to enhance reactivity and performance in Ionic apps built with Angular by working smoothly with the OnPush change detection and the future Signal based change detection.

I myself created wrapper around Ionic components to have such fields exposed as signals.

Describe the Use Case

Allows to easily listen to changes, and create computed values from inputs. Allows to easily use OnPush change detection, for example this, becomes possible and is reactive if used inside templates:

isEmpty() {
    this.myInput().value() === "" || this.myInput().value() === undefined || this.myInput().value() === null
}

Describe Preferred Solution

Just expose a field which would hold the current input value as a signal.

Describe Alternatives

No response

Related Code

No response

Additional Information

No response

[liamdebeasi]

Thanks for the report. I am going to close this since this behavior is already achievable in Ionic Framework. Developers should use the model signal to have reactive signals with Ionic component values:

<ion-searchbar [(ngModel)]="searchbarValue"></ion-searchbar>

import { model } from '@angular/core';

...

searchbarValue = model('123');