Skip to content

Latest commit

History

History
60 lines (33 loc) 路 1.58 KB

File metadata and controls

60 lines (33 loc) 路 1.58 KB

Async Dependency Initialization with requireValue (Riverpod)

How do you initialize an async dependency during app startup, and use it synchronously afterwards?

With Riverpod, this is done in 3 simple steps:

  1. Declare it inside a FutureProvider
  2. Initialize it inside main()
  3. Use requireValue afterwards

Details in thread below 馃У


The key steps are to:

  • declare and initialize the dependency inside a FutureProvider
  • access the dependency with requireValue whenever needed (inside other providers or widgets)

But requireValue will throw unless there is a value already.


To address this, we can create a ProviderContainer inside main() and await until the FutureProvider is initialized.


As a result, any providers or widgets that depend (directly or indirectly) on the original FutureProvider only contain synchronous code.

So no await or .when is needed.


I used to solve this problem by:

  • throwing an UnimplementedError inside the FutureProvider
  • initializing the dependency with a provider override inside main()

But this approach much nicer and easier to follow. 馃檪

Happy coding!


Found this useful? Show some love and share the original tweet 馃檹


Previous Next
8 Steps to Follow When Building Your Next Flutter App Highlight oversized images with the Flutter DevTools