Alex Rickabaugh 2b254bc050 fix(core): linkedSignal.update should propagate errors ...

Unlike a normal `signal()`, a `linkedSignal()` can be in an error state when
its computation fails. Currently, there's a bug where `linkedSignal.update`
does not account for this error state, and will pass the internal `ERRORED`
`Symbol` as the current value to the updater function.

This commit fixes the issue by having `update()` check and throw the error
instead of calling the updater function.

(cherry picked from commit aff9e36a98)

2026-02-02 12:21:36 -08:00

..

BUILD.bazel

build: rename defaults2.bzl to defaults.bzl (#63383)

2025-08-25 15:45:01 -07:00

computed_spec.ts

refactor(core): convert scripts within packages/core/test to relative imports (#60227)

2025-03-25 10:58:00 -07:00

effect_util.ts

refactor(core): convert scripts within packages/core/test to relative imports (#60227)

2025-03-25 10:58:00 -07:00

glitch_free_spec.ts

refactor(core): convert scripts within packages/core/test to relative imports (#60227)

2025-03-25 10:58:00 -07:00

is_signal_spec.ts

refactor(core): expose isWritableSignal to the publicApi

2025-10-29 20:31:41 +00:00

linked_signal_spec.ts

fix(core): linkedSignal.update should propagate errors

2026-02-02 12:21:36 -08:00

non_reactive_spec.ts

refactor(core): convert scripts within packages/core/test to relative imports (#60227)

2025-03-25 10:58:00 -07:00

signal_spec.ts

refactor(core): Delete createSignalTuple (#61907)

2025-06-06 13:46:16 +02:00

watch_spec.ts

refactor(core): convert scripts within packages/core/test to relative imports (#60227)

2025-03-25 10:58:00 -07:00