`AsyncPipe.transform` will never return `undefined`, even when passed
`undefined` in input, in contrast with what was declared in the
overloads.

Additionally the "actual" method signature can be updated to match the
most generic case, since the implementation does not rely on wrappers
anymore.

BREAKING CHANGE:
The async pipe no longer claims to return `undefined` for an input that
was typed as `undefined`. Note that the code actually returned `null` on
`undefined` inputs. In the unlikely case you were relying on this,
please fix the typing of the consumers of the pipe output.

PR Close #37447

Make typing of DatePipe stricter to catch some misuses (such as passing
an Observable or an array) at compile time.

BREAKING CHANGE:
The signature of the `date` pipe now explicitly states which types are
accepted. This should only cause issues in corner cases, as any other
values would result in runtime exceptions.

PR Close #37447

Make typing of number pipes stricter to catch some misuses (such as
passing an Observable or an array) at compile time.

BREAKING CHANGE:
The signatures of the number pipes now explicitly state which types are
accepted. This should only cause issues in corner cases, as any other
values would result in runtime exceptions.

PR Close #37447

I18nPluralPipe can actually accept `null` and `undefined` (which are
convenient for composing it with the async pipe), but it is currently
typed to only accept `number`.

PR Close #37447

As shown in the tests, `KeyValuePipe.transform` can accept
`undefined`, in which case it always returns `null`.

Additionally, the typing for `string` keys can be made generic, so the
comparison function is only required to accept the relevant cases.

Finally, the typing for `number` records now shows that the comparison
function and the result entries will actually receive the string version
of the numeric keys, just as shown in the tests.

BREAKING CHANGE:
The typing of the `keyvalue` pipe has been fixed to report that for
input objects that have `number` keys, the result will contain the
string representation of the keys. This was already the case and the
code has simply been updated to reflect this. Please update the
consumers of the pipe output if they were relying on the incorrect
types. Note that this does not affect use cases where the input values
are `Map`s, so if you need to preserve `number`s, this is an effective
way.

PR Close #37447

Even in the overloads, state that it can accept `null` and
`undefined`, in order to ensure easy composition with `async`.

Additionally, change the implementation to return `null` on an
`undefined` input, for consistency with other pipes.

BREAKING CHANGE:
The `slice` pipe now returns `null` for the `undefined` input value,
which is consistent with the behavior of most pipes. If you rely on
`undefined` being the result in that case, you now need to check for it
explicitly.

PR Close #37447

… in Angular Pipes

There is an upcoming improvement in common pipes in Angular framework that would be released in the next major version (v11). The changes can be found in angular/angular#37447.

This commit refactors `IgxDatePipeComponent` and `IgxDecimalPipeComponent` pipes to provide forward-compatibility for the next major release of Angular framework. The improved typings make `transform` function signatures of the mentioned pipes incompatible with the `DatePipe` and `DecimalPipe`. This commit updates the mentioned pipes to initialize `DatePipe` and `DecimalPipe` in constructors instead of extending them (to keep existing `transform` function signatures) and use created instances inside the `transform` function as needed.

…ular Pipes

There is an upcoming improvement in common pipes in Angular framework that would be released in the next major version (v11). The changes can be found in angular/angular#37447.

This commit refactors the `CNCurrencyPipe` pipe to provide forward-compatibility for the next major release of Angular framework. The improved typings make `transform` function signature of the mentioned pipe incompatible with the `CurrencyPipe`. This commit updates the `CNCurrencyPipe` pipe to initialize the `CurrencyPipe` in constructor instead of extending it (to keep existing `transform` function signature) and use created instance inside the `transform` function as needed.

…ular Pipes

There is an upcoming improvement in common pipes in Angular framework that would be released
in the next major version (v11). The changes can be found in
angular/angular#37447.

This commit refactors the `CNCurrencyPipe` pipe to provide forward-compatibility for the next
major release of Angular framework. The improved typings make `transform` function signature
of the mentioned pipe incompatible with the `CurrencyPipe`. This commit updates the
`CNCurrencyPipe` pipe to initialize the `CurrencyPipe` in constructor instead of extending it
(to keep existing `transform` function signature) and use created instance inside the `transform`
function as needed.

…ular Pipes

There is an upcoming improvement in common pipes in Angular framework that would be released
in the next major version (v11). The changes can be found in
angular/angular#37447.

This commit refactors the `CNCurrencyPipe` pipe to provide forward-compatibility for the next
major release of Angular framework. The improved typings make `transform` function signature
of the mentioned pipe incompatible with the `CurrencyPipe`. This commit updates the
`CNCurrencyPipe` pipe to initialize the `CurrencyPipe` in constructor instead of extending it
(to keep existing `transform` function signature) and use created instance inside the `transform`
function as needed.