Meta

| Name | Description | | -----| ----------- | | Version | 0.1.0 | | Scope | View |

Problem Statement

As of now, StreamBuilder is used to consume data from EventBus. This results in repetition of code in initialData and stream. The snapshot data is also checked for null.

StreamBuilder<BmiViewModel>(
  initialData: context.fetch<BmiViewModel>(),
  stream: context.select<BmiViewModel>(),
  builder: (context, snapshot) => WeightText(
    text: snapshot.data!.weight,
  ),
),

Proposed Solution

A new widget called View can be created to hide this complexity.

Changes

1. Create a new widget View.
2. Create a new widget ViewWithContext to provide context.
3. Create a new widget DataWidget to facilitate inheritance.
4. Update tests.
5. Update example.
6. Update Readme.

Meta

| Name | Description | | -----| ----------- | | Version | 0.0.1 | | Scope | event_bus_provider |

Problem Statement

As of now, EventBus is retrieved from a widget as follows:

final bus = EventBusProvider.of(context);
bus.publish(IncrementEvent());
bus.select<Counter>()

The first line of code is a little bit of extra work every time we need an EventBus.

Proposed Solution

We can create an extension method for the BuildContext and use it like this:

context.dispatch(IncrementEvent());
context.select<Counter>();
context.save(Counter());
context.fetch<Counter>();

Changes

1. Add EventBusOnBuildContextExtension.
2. Add DispatchOnBuildContextExtension.
3. Add PublishOnBuildContextExtension.
4. Add SelectOnBuildContextExtension.
5. Add SaveOnBuildContextExtension.
6. Add FetchOnBuildContextExtension.
7. Update example.
8. Update Readme.
9. Update documentation.

Meta

| Name | Description | | -----| ----------- | | Version | 0.0.1 | | Scope | EventBusProvider |

Problem Statement

There is no way a widget can now access EventBus from zam_event_bus package.

Proposed Solution

An InheritedWidget can be created to pass the EventBus down the line.

New Components

1. EventBusProvider