Changes since 25.2.0-alpha2
New features
- Add overloaded fromInputStream method with fileNameOverride
Commit · Pull request · Issue
Fixes
-
Prevent multiple effect invocations when reading the same signal multiple times
Commit · Pull request · IssueWhen an effect reads the same signal multiple times (e.g. signal.get() called 3 times), each call creates a separate Usage instance and registers a separate listener. When the signal changes, all listeners fire, causing the effect to run multiple times instead of once. Added an AtomicBoolean flag in Effect.revalidate() that ensures onDependencyChange is called only once per change event, even if multiple usages refer to the same signal. The flag is reset on each revalidate() call so subsequent signal changes can trigger the effect again.