feat: 🎸 fix input/output type inference

[kfrancois]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngneat/spectator/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

The following types are not inferred correctly:

• InputFunction with transform
• OutputRef

Issue Number: #649

What is the new behavior?

Types are properly inferred when using output() or when using input() with transform set.

Does this PR introduce a breaking change?

[X] Yes
[ ] No

I believe the required peerDependency should now be Angular 17.3.0 - I didn't update this yet but I believe it's necessary (I have not yet checked the behaviour in a repo running an older version)

Other information

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[NetanelBasal]

This is a breaking change because it requires a specific version of Angular. I don't mind to release a major version but you should include it in the peer dependency and the commit message

[kfrancois]

Understood! I'll push this later today or tomorrow. Thank you for following up so quickly on this 😄

[kfrancois]

Added - it's a shame this type got changed in a minor version, since I do believe semantically it's a breaking change in Angular.

Any conditional types that relied on extends InputSignal broke. I suppose the Angular team considered this as an internal type (or simply forgot about it/thought it wasn't worth the breaking change).