No, it is not.
Currently there is only one active signature: startWith(...values)
Apart from this signature, it has several overloads which accept scheduler: SchedulerLike
as the latest parameter: startWith(...values, scheduler) and this functionality has been deprecated.
If you don't use scheduler
with startWith
you are fine.
If you do, then you need rewrite your code using scheduled
function like they suggest in the comment beside depreciation annotation: scheduled([[a, b, c], source], scheduler).pipe(concatAll())
.
Highly likely, you are using startWith(null)
or startWith(undefined)
, they are not deprecated despite the notice, but IDE detects a wrong function signature, which is deprecated, and shows the warning.
Or, you are using formControl.valueChanges
which emits any
type, or any other observable stream with any
. Because any
matches the SchedulerLike
, you see the notice.
Therefore, try to avoid any
via adding filter((v): v is number => typeof === 'number')
or any other possible way.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…