Computed signals and Effects should produce runtime warning if dependencies reaches zero about angular

[jonahbron]

For reference to anyone else who runs into this issue in the meantime, there are a couple of solutions; one is to ensure range is always checked.

  effect(() => {
    const range = this.range();
    this.calendarRef?.setInput('selected', range);
  });

But I felt that this solution could be brittle; someone (even myself in the future) could easily come along and think that factoring out that variable is okay. That could be defended against with a comment like this that standardizes the practice of evaluating dependent signals unconditionally:

  effect(() => {
    const range = this.range();
    // ^ Evaluate all signals first ^
    this.calendarRef?.setInput('selected', range);
  });

But the solution I settled on instead was to turn calendarRef itself into a signal. Then the optional chaining all works as expected.

  effect(() => {
    this.calendarRef()?.setInput('selected', this.range());
  });