[0.14.0] Stateless Widget

[MichalNemec]

Description

Why fileLoader is not disposed by default or with bool property? Right now when we use rive file, we need to have stateful widget to dispose FileLoader.

Expected behavior

An option to use stateful widget, but also stateless widget for simple rives.

Device & Versions (please complete the following information)

• Device: Android Emulator
• OS: Android SDK API Level 31
• Flutter Version:

Flutter 3.32.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 5c1433509f (7 weeks ago) • 2025-06-11 13:12:24 -0700
Engine • revision 31c4875c7a (8 weeks ago) • 2025-06-05 08:39:10 -0700
Tools • Dart 3.8.1 • DevTools 2.45.1

Additional context

RiveWidgetBuilder(
        fileLoader: FileLoader.fromAsset('file.riv', riveFactory: rive.Factory.rive),
        disposeLoader: true, // <-- Something like this
        dataBind: const AutoBind(),
        onLoaded: _handleRiveLoaded,
        builder: (context, state) => switch (state) {
          RiveLoading() => const CircularProgressIndicator(),
          RiveFailed() => Text('Failed to load: ${state.error}'),
          RiveLoaded() => RiveWidget(controller: state.controller, fit: Fit.cover),
        },
      ),

[HayesGordon]

This is to ensure reusability and to clearly indicate ownership. If you don't dispose of this FileLoader, you can reuse it on a different screen or in multiple locations without needing to parse the same .riv file again and again, which can be computationally expensive. It would also allow you to preload/parse the .riv file and share it through other state management techniques (not necessarily using a stateful widget).

In the past, file creation and ownership were hidden from the end user for some portion of the API. This resulted in users easily misusing or misunderstanding when they should use a different API to take ownership of the file's life cycle. Or they never took the time to consider that they should own the file, which resulted in misuse.

You can easily create your own wrapper widget if you prefer a simpler pattern. But again, if someone creates their own wrapper, at least they are intentional about it!

I'm happy to hear further arguments, though, or suggestions on an alternative API

[MichalNemec]

I fully understand the choice. I created my own wrapper and now i can have stateless widgets again for simple one off rives but also for long lasting ones.