Could you upgrade the instructions as i want to play around with this example...

env: x-MacBook-Pro:chat_app apple$ flutter doctor [✓] Flutter (on Mac OS, channel master) • Flutter at /usr/local/flutter/flutter • Framework revision 16ce090fde (5 hours ago), 2016-11-01 20:34:36 • Engine revision 63e71803de • Tools Dart version 1.21.0-dev.2.0

[✓] Android toolchain - develop for Android devices (Android SDK 24.0.3) • Android SDK at /Users/apple/Library/Android/sdk • Platform android-24, build-tools 24.0.3 • ANDROID_HOME = /Users/apple/Library/Android/sdk • Java(TM) SE Runtime Environment (build 1.8.0_60-b27)

[✓] iOS toolchain - develop for iOS devices (Xcode 8.1) • XCode at /Applications/Xcode.app/Contents/Developer • Xcode 8.1, Build version 8B62

[x] Flutter IDE Support (No supported IDEs installed) • IntelliJ - https://www.jetbrains.com/idea/

[✓] Connected devices • None x-MacBook-Pro:chat_app apple$

error:

x-MacBook-Pro:chat_app apple$ pwd
/Users/apple/workspace/go/src/github.com/flutter/flutter_flux/example/chat_app
x-MacBook-Pro:chat_app apple$ pub get
Could not find a file named "pubspec.yaml" in "/Users/apple/workspace/go/src/github.com/flutter/flutter_flux/example/chat_app".
x-MacBook-Pro:chat_app apple$ 

IDE: VSCode

Doesn't seem to preclude builds and debugging, however is triggering a heap of 'errors' in analyzer.

Thoughts?

`[✓] Flutter (Channel dev, v0.10.1, on Mac OS X 10.13.6 17G65, locale en-NZ) • Flutter version 0.10.1 at /Users/greg/Library/Developer/flutter • Framework revision 6a3ff018b1 (13 days ago), 2018-10-18 18:38:26 -0400 • Engine revision 3860a43379 • Dart version 2.1.0-dev.7.1.flutter-b99bcfd309

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3) • Android SDK at /Users/greg/Library/Android/sdk • Android NDK at /Users/greg/Library/Android/sdk/ndk-bundle • Platform android-28, build-tools 28.0.3 • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06) • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1) • Xcode at /Applications/Xcode.app/Contents/Developer • Xcode 10.1, Build version 10B61 • ios-deploy 1.9.2 • CocoaPods version 1.5.3

[✓] Android Studio (version 3.2) • Android Studio at /Applications/Android Studio.app/Contents • Flutter plugin version 29.1.1 • Dart plugin version 181.5656 • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06) [✓] VS Code (version 1.28.2) • VS Code at /Applications/Visual Studio Code.app/Contents • Flutter extension version 2.19.0

[!] Connected device ! No devices available! Doctor found issues in 1 category.greg@iMac:~/Projects/Tierra/logmate_flutter$`

in store.dart,

class Store {
    // ...
void triggerOnConditionalAction<T>(Action<T> action, bool onAction(T payload)) {
    assert(action != null);
    action.listen((dynamic payload) async {
      // Action functions must return bool, or a Future<bool>.
      dynamic result = onAction(payload);
      bool wasChanged;
      if (result is Future) {
        wasChanged = await result;
      } else {
        wasChanged = result;
      }
      if (wasChanged) {
        trigger();
      }
    });
  }
    // ...
}

the 2nd param onAction defined bool return type. it should be dynamic.

In the example, when we commit a new message, the _currentMessage is emptied but the TextField does not reflect that changes.

This is the code in the store:

triggerOnAction(commitCurrentMessageAction, (ChatUser me) {
      final ChatMessage message =
          new ChatMessage(sender: me, text: _currentMessage);
      _messages.add(message);
      _currentMessage = '';
    });

The view uses a TextEditingController as a controller for the TextField Widget so I understand why it is not updated.

How can we empty the TextField from the Store with flutter_flux?

Which means moving to new Gradle build as well as some changes in the Flutter API itself (ListTile instead of ListItem, ListView instead of Block, etc.).

I've already done so locally and got the app running with today's Flutter version. I can also submit a pull request, but should I put the updated example in a new folder or just overwrite example/chap_app?

Apparently "flutter run" includes the "pub get" step.

chat_app [master]$ flutter run Running 'flutter packages get' in chat_app... 2419ms New users installing Flutter won't necessarily know about the "pub" tool, so removing it will reduce friction for those users.

• Rather than using complex mixin inheritance, we now use composition for StoreListener.
• Rename StoreWatcher.initState to StoreWatcher.initStores to suggest that this function is for initializing the stores rather than initializing the (hidden) state object.
• Update the dartdocs to reflect how the code works currently.

I am referring to the example provided in this repo. https://github.com/google/flutter_flux/blob/master/example/lib/main.dart#L62

The handleChatMessageStoreChanged function is called with the Store parameter and from the example it looks like, the downcasted store is assigned to a local scoped store and not the widget's store directly.

Can that function be written as

class ChatScreenState extends State<ChatScreen>
    with StoreWatcherMixin<ChatScreen> {
  // Never write to these stores directly. Use Actions.
  ChatMessageStore messageStore;
  // ...
  void handleChatMessageStoreChanged(Store store) {
    // ChatMessageStore messageStore = store; // instead of this local scoped store ...
    messageStore = store; // ... assign to widget's store
    if (messageStore.currentMessage.isEmpty) {
        msgController.clear();
    }
    setState(() {});
  }
  // ...
}

If this is not okay, I would like to know why.

After this patch, we now depend on package:flutter using an SDK source, which means package:flutter doesn't need to be at a particular path relative to this package anymore.

I'm getting the following error:

Because cronicalia_flutter depends on flutter_flux >=4.0.1 which requires SDK version >=1.19.0 <2.0.0, version solving failed.

Could you update the pubspec.yaml? Instead of

environment:
  sdk: ">=1.24.0 <2.0.0"

use

environment:
  sdk: ">=1.24.0 <3.0.0"

Hi,

I've been wrestling with this for a while now and can't see what is going wrong, but my StoreWatcherMixin widget does not get build() called after setting state in the flux store.

Main.dart:

void main() => runApp(new MyApp());

class MyApp extends StatefulWidget {
  @override
  State createState() => new AppState();
}

class AppState extends State<MyApp>
  with StoreWatcherMixin<MyApp> {

  var appStore;

  @override
  void initState() {
    super.initState();
    appStore = listenToStore(_appStoreToken);
  }

  @override
  Widget build(BuildContext context) {
      ...
      return new SecondPage(_appStoreToken);
   }

The store:

final Action<List<Foo>> setFoos = new Action<List<Foo>>();
final AppStore _store = new AppStore();
final StoreToken _appStoreToken = new StoreToken(_store);

class AppStore extends Store {
  List<Foo> _allFoos = new List<Foo>();
  List<ArkhamDBCardPack> get allFoos => _allFoos;

  AppStore() {
    triggerOnAction(setFoos, (value) => _allFoos = value);
  }
}

Second page:

class SecondPage extends StatefulWidget {

  final StoreToken _storeToken;
  SecondPage(this._storeToken);

  @override
  State createState() => new SecondPageState(_storeToken);
}

class SecondPageState extends State<SecondPage>
  with StoreWatcherMixin<SecondPage> {

  var appStore;
  final StoreToken _storeToken;
  List<Foo> foos;

  SecondPageState(this._storeToken);

  @override
  void initState() {
    super.initState();
    debugPrint('x');
    appStore = listenToStore(_storeToken);
    foos = appStore.allFoos;
  }

  @override
  Widget build(BuildContext context) {
    debugPrint('rebuilding');
    return new IconButton(
              icon: new Icon(Icons.refresh),
              onPressed: () async {
                var data = await fetchFoos();
                setFoos.call(data);
              },
            )
   }
}

This isn't the exact code, but its close enough. The first time it runs, I press the button on the second page to fetch the data and call setFoos. debugPrints show that it has set the value correctly into the store, but the build() and debugPrint('rebuilding') are never called a second time.

What am I doing wrong? I really want to get this working as flutter and flux seem like a great tech. Thanks in advance!

If a method is listening to an action then for first time it gets hit once, then for next time if user gets back to the same page then the method gets hit twice and on third time its 3 times and increases every time.

Below is a code to simulate the same on click of Next a action is called and on action change the user is taken to second page, but on second time the action listening method gets hit twice.

    import 'package:flutter/material.dart';
    import 'package:flutter_flux/flutter_flux.dart';

    void main() => runApp(MyApp());

    class MyApp extends StatelessWidget {
      @override
      Widget build(BuildContext context) {
        return MaterialApp(
          home: MyHome(),
        );
      }
    }
    //========
    class MyHome extends StatefulWidget {
      @override
      _MyHomeState createState() => _MyHomeState();
    }

    class _MyHomeState extends State<MyHome> with StoreWatcherMixin<MyHome>  {
      AppStore store;
      @override
      void initState() {
        store = listenToStore(appStoreToken);
        changeStatus.listen(_openSetupDialogue);
        super.initState();
      }

      void _openSetupDialogue(dynamic payload){
        if(payload == true) {
          print("method got hit");
          Navigator.push(context, MaterialPageRoute(builder: (context) => SecondPage()));
        }
      }

      @override
      Widget build(BuildContext context) {
        return RaisedButton(
          child: Text("Next"),
          onPressed: (){
            changeStatus(true);
          },
        );
      }
    }
    //===========
    class SecondPage extends StatefulWidget {
      @override
      _SecondPageState createState() => _SecondPageState();
    }

    class _SecondPageState extends State<SecondPage> {
      @override
      Widget build(BuildContext context) {
        return RaisedButton(
          child: Text("back"),
          onPressed: (){Navigator.push(context, MaterialPageRoute(builder: (context) =>MyHome()),
            );
          },
        );
      }
    }
    //===========
    class AppStore extends Store {
      bool state = true;
      AppStore(){
        triggerOnAction(changeStatus, (status){
          state = status;
        });
      }
      bool get getAppStore => state;
    }
    final Action changeStatus = Action<bool>();
    final appStoreToken = StoreToken(AppStore());

There are some tab pages like fragment on android, I use constructor arguments to conotrol their stores. Like this:

List<GankPage> pages = [
  TabPage('aaa'),
  TabPage('bbb'),
]

class TabPage extends StoreWatcher {
  String type;
  StoreToken pageStoreToken;
  TabPage({Key k, this.type}) : super(key: k);

  @override
  void initStores(ListenToStore listenToStore) {
    pageStoreToken = StoreToken(PageStore(this.type));
    listenToStore(pageStoreToken);
    pageAction.call();
  }

}

If I write like this, when I switch tab the old actions will be called. I saw the note is that stores should not depend on any constructor parameters. Any suggetions?

The title of this issue could be a little misleading but I was not sure how else to describe my thought process, so please stay with me and read along.

I am writing a Flutter application that uses flutter_flux. I have a few stores and a few views (widgets) so far. Right now I am in a dilemma on how to do the network API calls. My widget loads but does not have any data to display yet, which is fine, but now it needs to call my network API service that responds with data. Here is what I am thinking design-wise. Please share your opinions on it.

Widget -> Action -> Store -> Network Service Call -> trigger()

In this design, the widget kicks off an action something like fetchMessages and the store listening to this action MessageStore receives a call to this action. In the action callback, this store kicks the network call that returns Future. In the then() callback of that Future, this store mutates it's own data and calls trigger() so that the original view that started this now receives a callback. Similarly, also in catchError of the same Future, this store calls trigger() with some other mutation that maintains error states.

In this design, I am not exactly sure where do I call action from the widget? In build or in initState? My thinking is that in initState the widget will grab data from store but it will be null or empty initially, and build will render empty view but at the same time, kickstarts the cycle described above, which calls back to the widget later and the build function now has data to render, re-grabbed from store.

Do you think it is a good pattern? It still abides to Flux's unidirectional data flow and does not let store data to be manipulated in any way other than an action callback.