Upgrade to Angular 20

[timdeschryver]

Revisit #413

[lacolaco]

@timdeschryver What are your thoughts on the new bindings API for creating dynamic components in v20? In my opinion, ATL's current interfaces for inputs and outputs are unnecessary.

TestBed.createComponent(MyDialog, {
  bindings: [
    // Bind a signal to the `canClose` input.
    inputBinding('canClose', canClose),

    // Listen for the `onClose` event specifically on the dialog.
    outputBinding<Result>('onClose', result => console.log(result)),
   
    // Creates two way binding with the title property
    twoWayBinding('title', title),
  ],
})

[timdeschryver]

@timdeschryver What are your thoughts on the new bindings API for creating dynamic components in v20? In my opinion, ATL's current interfaces for inputs and outputs are unnecessary.

TestBed.createComponent(MyDialog, {
  bindings: [
    // Bind a signal to the `canClose` input.
    inputBinding('canClose', canClose),

    // Listen for the `onClose` event specifically on the dialog.
    outputBinding<Result>('onClose', result => console.log(result)),
   
    // Creates two way binding with the title property
    twoWayBinding('title', title),
  ],
})

@lacolaco thanks for bringing this up. I wasn't aware that v20 included this feature.
I think this can be useful within ATL.
We can add this as an additional API without deprecating/removing the current API (we can revisit this later). The only question that I currently have is how this API behaves with rerendering the component.

If you want you can propose/implement this feature, as I believe it can be beneficial (for us and the users).

[lacolaco]

@timdeschryver Appreciate the feedback! I'll be working on a draft design for the interop and then I'll investigate the rerendering issue.

[timdeschryver]

@timdeschryver Appreciate the feedback! I'll be working on a draft design for the interop and then I'll investigate the rerendering issue.

The rerendering should not be blocking IMHO.
Thanks in advance @lacolaco