This repository was archived by the owner on Dec 11, 2025. It is now read-only.
This repository was archived by the owner on Dec 11, 2025. It is now read-only.
toUnSignal should handle UnComputed inputs to maintain reactivity #56
Description
Problem
Currently toUnSignal only detects isUnSignal and skips over UnComputed<T> values, meaning computed inputs in MaybeUnRef<T> fall through to the default case and lose reactivity.
Solution
Add a check for isUnComputed after the existing isUnSignal check to convert UnComputed inputs into live UnSignal wrappers.
Context
This issue was identified during the review of PR #55 (useToggle implementation) but is unrelated to that specific feature and affects the broader toUnSignal functionality.
Related:
- PR: feat: useToggle #55
- Comment: feat: useToggle #55 (comment)
Reported by: @Shinigami92