Logging and error reporting

Riverpod natively offers a way to listen to all events happening in the provider tree.
This can be used to log all the events or to report errors to a remote service.

This is achieved by using the ProviderObserver class, and passing it to ProviderScope/ProviderContainer.

Defining a ProviderObserver

A ProviderObserver is a class that should be extended.
It offers various methods which can be overridden to listen to events:

• didAddProvider, called when a provider is added to the tree
• didUpdateProvider, called when a provider is updated
• didDisposeProvider, called when a provider is disposed
• providerDidFail, when a synchronous provider throws an error

class MyObserver extends ProviderObserver {
  @override
  void didAddProvider(
    ProviderObserverContext context,
    Object? value,
  ) {
    print('Provider ${context.provider} was initialized with $value');
  }

  @override
  void didDisposeProvider(ProviderObserverContext context) {
    print('Provider ${context.provider} was disposed');
  }

  @override
  void didUpdateProvider(
    ProviderObserverContext context,
    Object? previousValue,
    Object? newValue,
  ) {
    print(
      'Provider ${context.provider} updated from $previousValue to $newValue',
    );
  }

  @override
  void providerDidFail(
    ProviderObserverContext context,
    Object error,
    StackTrace stackTrace,
  ) {
    print('Provider ${context.provider} threw $error at $stackTrace');
  }
}

Using a ProviderObserver

Now that we've defined an observer, we need to use it.
To do so, we should pass it to either ProviderScope or ProviderContainer:

runApp(
  ProviderScope(
    observers: [
      MyObserver(),
    ],
    child: MyApp(),
  )
);

final container = ProviderContainer(
  observers: [
    MyObserver(),
  ],
);