computedAsync should not be `| undefined` if an `initialValue` is provided
NateRadebaugh opened this issue · comments
For cases where an initialValue
is provided, the type of computedAsync
's returned signal should not have | undefined
in it by default.
For instance, if I'm computing a full object, I'd prefer not to have file()?.src
, file()?.width
, file()?.height
etc everywhere in my templates (since we know signals don't properly type narrow).
Is this something that's feasible or was there an explicit design decision to mark computedAsync
as always possibly undefined
?
I can't reproduce in my stackblitz, so it must be something wrong with my setup. closing, sorry for the churn