Computed signal and effect don't recompute if non signal boolean value included in computation as first check in condition. about angular HOT 7 CLOSED

Hi, booleanSignal i being read in both cases. && operators have to read and evaluate both conditions.
computed(() => this.boolean && this.booleanSignal())

This is not the case - if the first condition is false, the subsequent expression will not be evaluated: https://stackblitz.com/edit/vitejs-vite-gy878w?file=main.js&terminal=dev

from angular.

In that sense, this is "working as intended" from an Angular perspective. However, it does raise the question of whether computed prohibit (or perhaps warn about) the degenerate case of no dependencies?

from angular.

Are you speaking in terms of like, the language service or compiler giving a warning/error? If so, I think that would be nice.

It can't be compiler, any potential warning would have be runtime

from angular.

from angular.

this is very unintuitive behaviour and shouldn't work like this when documentation states ant computed signal will recompute when signal inside changes.

This should be nuanced with the statement that "computed signal will recompute when accessed signal inside changes". In your second example there is no signal read at all at we were considering a warning in such cases.

from angular.

this is very unintuitive behaviour and shouldn't work like this when documentation states ant computed signal will recompute when signal inside changes.

This should be nuanced with the statement that "computed signal will recompute when accessed signal inside changes". In your second example there is no signal read at all at we were considering a warning in such cases.

Hi, booleanSignal i being read in both cases. && operators have to read and evaluate both conditions.
computed(() => this.boolean && this.booleanSignal())

from angular.

However, it does raise the question of whether computed prohibit (or perhaps warn about) the degenerate case of no dependencies?

Are you speaking in terms of like, the language service or compiler giving a warning/error? If so, I think that would be nice.

from angular.