Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / uptech/flutter_forge issues and pull requests

#18 - Add builder pattern to ComponentWidget

Issue - State: closed - Opened by drewdeponte over 1 year ago - 2 comments

#17 - Add test coverage for `view_store.dart`

Issue - State: open - Opened by drewdeponte almost 2 years ago

#16 - Add test coverage to `async_state_widget.dart` & `async_state.dart`

Issue - State: open - Opened by drewdeponte almost 2 years ago

#15 - Explore using Dart 3 records in place of ReducerTuple

Issue - State: open - Opened by drewdeponte almost 2 years ago - 1 comment

#14 - WIP: add ability to bridge Riverpod providers

Pull Request - State: closed - Opened by drewdeponte about 2 years ago

#13 - Create example of using flutter forge component in app that uses state based navigation

Issue - State: open - Opened by drewdeponte over 2 years ago

#12 - Create example of using a component in an app that isn't using state based navigation

Issue - State: closed - Opened by drewdeponte over 2 years ago - 1 comment

#11 - Think through & figure out overwriting UI in child components of components

Issue - State: open - Opened by drewdeponte over 2 years ago

#10 - Setup a basic test suite for flutter_forge

Issue - State: open - Opened by drewdeponte over 2 years ago

#9 - Make the example main.dart file a full blown example

Issue - State: open - Opened by drewdeponte over 2 years ago

#8 - When popping examples off the stack an exception is thrown

Issue - State: closed - Opened by drewdeponte over 2 years ago - 1 comment
Labels: bug

#7 - Figure out how bring standardized state & mutation into the framework via composition.

Issue - State: open - Opened by drewdeponte over 2 years ago

#6 - Think through refreshing and how it maps to Riverpod proper in terms of rebuilds

Issue - State: open - Opened by drewdeponte over 2 years ago

#5 - Figure out how to support parent know about multiple stores with child knowing about one store

Issue - State: closed - Opened by drewdeponte over 2 years ago - 1 comment

#4 - explore separating out the flutter portion of the framework into a separate framework and what that would look like (this might help us more clearly see core primitives and how they should compose)

Issue - State: open - Opened by drewdeponte over 2 years ago

#3 - clean up the code base and turn it into an actual library and separate the examples out (look at riverpod as an example maybe)

Issue - State: closed - Opened by drewdeponte over 2 years ago - 1 comment

#2 - explore modularization further in Dart and how we can use it to simplify naming within components as well guiding/forcing isolation

Issue - State: open - Opened by drewdeponte over 2 years ago - 2 comments

#1 - come up with a good name for the framework

Issue - State: closed - Opened by drewdeponte over 2 years ago - 1 comment