signals_flutter library

Classes

AsyncSignal<T>

A compound Signal that wraps a Stream or Future

Computed<T>

Data is often derived from other pieces of existing data. The computed function lets you combine the values of multiple signals into a new signal that can be reacted to, or even used by additional computeds. When the signals accessed from within a computed callback change, the computed callback is re-executed and its new return value becomes the computed signal's value.

Connect<T>

Connects a Stream to a Signal.

FutureSignal<T>

A Signal that wraps a Future

IterableSignal<E>

A Signal that holds a Iterable.

ListSignal<E>

A Signal that holds a List.

LoggingSignalsObserver

MapSignal<K, V>

A Signal that holds a Map.

ReadonlySignal<T>

SetSignal<E>

A Signal that holds a Set.

Signal<T>

The signal function creates a new signal. A signal is a container for a value that can change over time. You can read a signal's value or subscribe to value updates by accessing its .value property.

SignalsObserver

StreamSignal<T>

A Signal that wraps a Stream

TimerSignal

Emit recurring TimerSignalEvent aka AsyncSignal

ValueSignal<T>

Signal that can be extended and used as a class

Watch<T extends Widget>

Watch is a drop-in replacement for Builder that will rebuild when any signals inside the builder change

Extensions

ReadonlySignalUtils on ReadonlySignal<T>

Signal extensions

SignalFutureUtils on Future<T>

Extension on future to provide helpful methods for signals

SignalIterableUtils on Iterable<T>

Extension on future to provide helpful methods for signals

SignalListUtils on List<T>

Extension on future to provide helpful methods for signals

SignalMapUtils on Map<K, V>

Extension on future to provide helpful methods for signals

SignalSetUtils on Set<T>

Extension on future to provide helpful methods for signals

SignalStreamUtils on Stream<T>

Extension on stream to provide helpful methods for signals

SignalUtils on Signal<T>

Mutable signal utils

SignalValueListenableUtils on ValueListenable<T>

Extension on ValueListenable to provide helpful methods for signals

SignalValueNotifierUtils on ValueNotifier<T>

Extension on ValueNotifier to provide helpful methods for signals

TimerSignalDurationUtils on Duration

Expose Duration as a TimerSignal

Functions

asyncSignalFromFuture<T>(Future<T> future(), {required T initialValue, String? debugLabel}) → AsyncSignal<T>

asyncSignalFromStream<T>(Stream<T> stream(), {required T initialValue, bool? cancelOnError, String? debugLabel}) → AsyncSignal<T>

batch<T>(BatchCallback<T> callback) → T

The batch function allows you to combine multiple signal writes into one single update that is triggered at the end when the callback completes.

clearSubscribers() → void

computed<T>(ComputedCallback<T> compute, {String? debugLabel}) → Computed<T>

Data is often derived from other pieces of existing data. The computed function lets you combine the values of multiple signals into a new signal that can be reacted to, or even used by additional computeds. When the signals accessed from within a computed callback change, the computed callback is re-executed and its new return value becomes the computed signal's value.

connect<T>(Signal<T> signal, [Stream<T>? stream]) → Connect<T>

Connects a Signal to a Stream.

disableSignalsDevTools() → void

effect(EffectCallback compute, {String? debugLabel}) → EffectCleanup

The effect function is the last piece that makes everything reactive. When you access a signal inside its callback function, that signal and every dependency of said signal will be activated and subscribed to. In that regard it is very similar to computed. By default all updates are lazy, so nothing will update until you access a signal inside effect.

futureSignal<T>(Future<T> compute(), {Duration? timeout, bool fireImmediately = false, String? debugLabel}) → FutureSignal<T>

Create a FutureSignal from a Future

iterableSignal<T>(Iterable<T> iterable, {String? debugLabel}) → IterableSignal<T>

Create an IterableSignal from Iterable

listenSignal<T>(BuildContext context, ReadonlySignal<T> signal, VoidCallback callback, {String? debugLabel}) → void

Used to listen for updates on a signal but not rebuild the nearest element

listSignal<T>(List<T> list, {String? debugLabel}) → ListSignal<T>

Create an ListSignal from List

mapSignal<K, V>(Map<K, V> map, {String? debugLabel}) → MapSignal<K, V>

Create an MapSignal from Map

setSignal<T>(Set<T> list, {String? debugLabel}) → SetSignal<T>

Create an SetSignal from Set

signal<T>(T value, {String? debugLabel}) → Signal<T>

The signal function creates a new signal. A signal is a container for a value that can change over time. You can read a signal's value or subscribe to value updates by accessing its .value property.

streamSignal<T>(Stream<T> stream(), {bool? cancelOnError, bool fireImmediately = false, String? debugLabel}) → StreamSignal<T>

Create a StreamSignal from a Stream

unlistenSignal<T>(BuildContext context, ReadonlySignal<T> signal) → void

Remove all subscribers for a given signal for listeners

untracked<T>(UntrackedCallback<T> callback) → T

In case when you're receiving a callback that can read some signals, but you don't want to subscribe to them, you can use untracked to prevent any subscriptions from happening.

unwatchElement(BuildContext context, {bool watch = true, bool listen = true}) → void

Remove all subscribers for a given context

unwatchSignal<T>(BuildContext context, ReadonlySignal<T> signal) → void

Remove all subscribers for a given signal for watchers

watchSignal<T>(BuildContext context, ReadonlySignal<T> signal, {String? debugLabel}) → T

Watch a signal value and rebuild the context of the Element if mounted and mark it as dirty

Typedefs

EffectCleanup = void Function()

Clean up function to stop subscriptions from updating the callback

MutableSignal<T> = Signal<T>

Signal that can read and write a value