flutter_solidart 0.4.2 copy "flutter_solidart: ^0.4.2" to clipboard
flutter_solidart: ^0.4.2 copied to clipboard

A simple State Management solution for Flutter applications inspired by SolidJS

0.4.2 #

  • BUGFIX: The Show widget now can work again with a ReadSignal.

0.4.1 #

  • CHORE: The ResourceBuilder now correctly handles a different Resource when the widget is updated.

0.4.0 #

  • BUGFIX: Listening to the source of a Resource was not stopped when the source disposed.
  • BUGFIX: A Resource would not perform the asynchronous operation until someone called the fetch method, typically the ResourceBuilder widget. This did not apply to the stream which was listened to when the resource was created. Now the behaviour has been merged and the fetch method has been renamed into resolve.
  • CHORE: Renamed ReadableSignal into ReadSignal.
  • CHORE: Renamed the readable method of a Signal into toReadSignal()

0.3.3 #

  • Add update extension on BuildContext. It's a convenience method to update a Signal value.

    You can use it to update a signal value, e.g:

    context.update<int>('counter', (value) => value * 2);
    

    This is equal to:

    // retrieve the signal
    final signal = context.get<Signal<int>>('counter');
    // update the signal
    signal.update((value) => value * 2);
    

    but shorter when you don't need the signal for anything else.

0.3.2 #

  • Add assert to resource fetch method to prevent multiple fetches of the same resource.
  • Fix ResourceBuilder that fetched the resource every time even if the resource was already resolved.

0.3.1 #

  • The select method of a signal now can take a custom options parameter to customize its behaviour.
  • Fixed an invalid assert in the ResourceBuilder widget that happens for resources without a fetcher.

0.3.0 #

  • Now Solid can deal also with SolidProviders. You no longer need an external dependency injector library. I decided to put some boundaries and stop suggesting any external dependency injector library. This choice is due to the fact that external libraries in turn provide state management and the user is more likely to mistakenly use solidart. I simplified the usage of InheritedWidgets with a very nice API:

    Declare providers #

    Solid(
          providers: [
            SolidProvider<NameProvider>(
              create: () => const NameProvider('Ale'),
              // the dispose method is fired when the [Solid] widget above is removed from the widget tree.
              dispose: (provider) => provider.dispose(),
            ),
            SolidProvider<NumberProvider>(
              create: () => const NumberProvider(1),
              // Do not create the provider lazily, but immediately
              lazy: false,
            ),
          ],
          child: const SomeChildThatNeedsProviders(),
      )
    

    Retrieve providers #

    final nameProvider = context.get<NameProvider>();
    final numberProvider = context.get<NumberProvider>();
    

    Provide providers to modals (dialogs, bottomsheets) #

      return showDialog(
        context: context,
        builder: (dialogContext) => Solid.value(
          // pass a context that has access to providers
          context: context,
          // pass the list of provider [Type]s
          providerTypes: const [NameProvider],
          child: Dialog(
            child: Builder(builder: (innerContext) {
              // retrieve the provider with the innerContext
              final nameProvider = innerContext.get<NameProvider>();
              return SizedBox.square(
                dimension: 100,
                child: Center(
                  child: Text('name: ${nameProvider.name}'),
                ),
              );
            }),
          ),
        ),
      );
    

    You cannot provide multiple providers of the same type in the same Solid widget.

0.2.2 #

  • createResource now accepts a stream and can be used to wrap a Stream and correctly handle its state.

0.2.1 #

  • Get a signal value with signalName().

0.2.0+1 #

  • Add documentation link inside the pubspec

0.2.0 #

  • Documentation improvements
  • Refactor Resource, now the createResource method takes only 1 generic, the type of the future result.
    // before
    final resource = createResource<SourceValueType, FetcherValueType>(fetcher: fetcher, source: source);
    // now
    final resource = createResource<FetcherValueType>(fetcher: fetcher, source: source); // the FetcherValueType can be inferred by Dart >=2.18.0, so you can omit it
    

0.1.4 #

  • Add official documentation link
  • Fix typo in fireImmediately argument name

0.1.3 #

  • Now Solid.value takes a list of [signalIds] and a [BuildContext]. You don't need anymore to get the signal first and pass it to Solid.value.
  • Set the minimum Dart SDK version to 2.18.

0.1.2+1 #

  • Update Readme

0.1.2 #

  • Add code coverage

0.1.1 #

  • Implement Solid.value to be able to pass Signals to modals

0.1.0+4 #

  • Add links to examples

0.1.0+3 #

  • Specify the type of resource to the ResourceBuilder

0.1.0+2 #

  • Decrease minimum Dart version to 2.17.0

0.1.0+1 #

  • Fix home page link

0.1.0 #

  • Initial version
47
likes
110
pub points
84%
popularity

Publisher

verified publishermariuti.com

A simple State Management solution for Flutter applications inspired by SolidJS

Repository (GitHub)
View/report issues

Documentation

Documentation
API reference

License

MIT (LICENSE)

Dependencies

collection, flutter, meta, solidart

More

Packages that depend on flutter_solidart