搜尋套件、儲存庫與 APP 分類

套件詳情v2.7.4

flutter_solidart

一個簡單的 Flutter 應用程式狀態管理解決方案,靈感來自 SolidJS

AndroidiOSWebmacOSWindowsLinux
近 30 天下載
6340
喜歡數
82
Pub 分數
160

安裝套件

flutter pub add flutter_solidart

套件介紹

根據套件公開資料產生的選型評估,僅供參考。

flutter_solidart 是一個輕量級的 Flutter 狀態管理解決方案,靈感來自 SolidJS 的響應式程式設計模型。它實現了細粒度的響應式更新,僅有受狀態變更影響的 UI 部分才會重新建構,從而提升效能。該套件使用響應式變數和衍生值來簡化狀態更新,無需冗長的樣板程式碼。它與 Flutter 的元件樹無縫整合,並支援所有主要平台。專為尋求簡單、高效替代傳統狀態管理方法的開發者設計。

適用情境

  • 表單中的即時資料更新
  • 透過最少的重構實現高效能的UI更新
  • 中小型應用中的簡單反應式邏輯
  • 跨多個組件的狀態共享
  • 建構響應式儀表板
  • 輕量級狀態管理,無需複雜設定

主要特色

  • 細粒度反應性
  • 最小化樣板程式碼
  • 響應式變數與衍生狀態
  • 自動依賴追蹤
  • 支援所有 Flutter 平台
  • 與現有組件的輕鬆整合

適合對象

  • 熟悉響應式程式設計的開發者
  • 需要快速UI更新的專案
  • 避免使用重型狀態管理框架的應用程式
  • 偏好簡單而非複雜
  • 快速原型設計使用者介面互動
  • 小型到中型 Flutter 應用程式

使用建議

  • 不適合具有複雜狀態的大型應用
  • 與成熟的替代方案相比,文件較少
  • 對於不熟悉響應式模式的使用者來說,學習曲線較陡
  • 比流行的狀態管理器社群支援少
  • 可能需要小心處理副作用
  • 最適合頻繁但局部狀態變更的應用程式

原始 README

以下為關聯原始碼儲存庫的 README 原文快照,最新內容請造訪原始碼儲存庫。

License: MIT GitHub stars Coverage GitHub issues GitHub pull-requests solidart Pub Version flutter_solidart Pub Version All Contributors

A simple state-management library inspired by SolidJS.

The objectives of this project are:

  1. Being simple and easy to learn
  2. Fits well with the framework's good practices
  3. Do not have a single global state, but multiple states only in the most appropriate places
  4. No code generation

Learning

For a comprehensive and updated documentation go to The Official Documentation

There are 5 main concepts you should be aware:

  1. Signal
  2. Effect
  3. Computed
  4. Resource
  5. Dependency Injection
Signal

Signals are the cornerstone of reactivity in solidart. They contain values that change over time; when you change a signal's value, it automatically updates anything that uses it.

To create a signal, you have to use the Signal class:

final counter = Signal(0);

The argument passed to the class is the initial value, and the return value is the signal.

To retrieve the current value, you can use:

print(counter.value); // prints 0

To change the value, you can use:

// Set the value to 2
counter.value = 2;
// Update the value based on the current value
counter.updateValue((value) => value * 2);
Effect

Signals are trackable values, but they are only one half of the equation. To complement those are observers that can be updated by those trackable values. An effect is one such observer; it runs a side effect that depends on signals.

An effect can be created by using the Effect class. The effect automatically subscribes to any signal and reruns when any of them change. So let's create an Effect that reruns whenever counter changes:

final disposeFn = Effect(() {
    print("The count is now ${counter.value}");
});
Computed

A computed signal is a signal that depends on other signals. To create a computed signal, you have to use the Computed class.

A Computed automatically subscribes to any signal provided and reruns when any of them change.

final count = Signal(0);
final doubleCount = Computed(() => count.value * 2);

Effect(() {
  print('The counter is ${count.value}');
  print('The double counter is ${doubleCount.value}');
});

count
  ..value = 1
  ..value = 2;

// The output will be:
// The counter is 0
// The double counter is 0
// The counter is 1
// The double counter is 2
// The counter is 2
// The double counter is 4
Resource

Resources are special Signals designed specifically to handle Async loading. Their purpose is wrap async values in a way that makes them easy to interact with.

Resources can be driven by a source signal that provides the query to an async data fetcher function that returns a Future.

The contents of the fetcher function can be anything. You can hit typical REST endpoints or GraphQL or anything that generates a future. Resources are not opinionated on the means of loading the data, only that they are driven by futures.

Let's create a Resource:

// The source
final userId = Signal(1);

// The fetcher
Future<String> fetchUser() async {
    final response = await http.get(
      Uri.parse('https://jsonplaceholder.typicode.com/users/${userId.value}/'),
      headers: {'Accept': 'application/json'},
    );
    return response.body;
}

// The resource
final user = Resource(fetchUser, source: userId);

A Resource can also be driven from a Stream instead of a Future, and can be created with Resource.stream(() => stream). In this case you just need to pass the stream field to the Resource class.

If you're using SignalBuilder you can react to the state of the resource:

SignalBuilder(
  builder: (_, __) {
    return user.state.when(
      ready: (data) {
        return Column(
          mainAxisSize: MainAxisSize.min,
          children: [
            ListTile(
              title: Text(data),
              subtitle:
                  Text('refreshing: ${userState.isRefreshing}'),
            ),
            userState.isRefreshing
                ? const CircularProgressIndicator()
                : ElevatedButton(
                    onPressed: user.refresh,
                    child: const Text('Refresh'),
                  ),
          ],
        );
      },
      error: (e, _) {
        return Column(
          mainAxisSize: MainAxisSize.min,
          children: [
            Text(e.toString()),
            userState.isRefreshing
                ? const CircularProgressIndicator()
                : ElevatedButton(
                    onPressed: user.refresh,
                    child: const Text('Refresh'),
                  ),
          ],
        );
      },
      loading: () {
        return const RepaintBoundary(
          child: CircularProgressIndicator(),
        );
      },
    );
  },
)

The on method forces you to handle all the states of a Resource (ready, error and loading). The are also other convenience methods to handle only specific states.

Dependency Injection

The dependency injection in flutter_solidart is done using the disco package.

This replaced the Solid widget which was used in the previous versions of flutter_solidart.

disco has been built on top of Solid to provide a more powerful and flexible way to handle dependency injection.

Refer to the official disco documentation which contains also examples written with flutter_solidart

DevTools

You can debug your application using the Solidart DevTools extension and filter your signals.

Contributors

Alexandru Mariuti
Alexandru Mariuti

💻 🐛 🚧 💬 👀 📖 ⚠️
manuel-plavsic
manuel-plavsic

💻
Luke Greenwood
Luke Greenwood

📖
9dan
9dan

💻 🐛 📖
Seven Du
Seven Du

💻 🐛 📖
Haresh Gediya
Haresh Gediya

💻

所屬分類

依賴

依賴清單 3 項

原始碼儲存庫

使用此套件的專案