You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 23, 2023. It is now read-only.
I'm not sure it's actually possible with Angular to do this. The transform method on the PipeTransform interface doesn't accept generic type information. https://angular.io/api/core/PipeTransform
However, if you find a way, feel free to inform me :)
It looks like it's actually possible (with some issues: angular/angular#21224), however it would require time to do this for all pipes which I don't have right now. Feel free to start a PR.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm submitting a ... (check one with "x")
Current behavior
all to
any
, no types any moreExpected behavior
keep types
Minimal reproduction of the problem with instructions
numbers: number[] = [1, 2, 3, 4, 5]
numbers | where: 1
is anany[]
notnumber[]
What is the motivation / use case for changing the behavior?
The text was updated successfully, but these errors were encountered: