Talker Documentation

Talker is a modular ecosystem for advanced error handling and logging in Dart and Flutter. It consists of several specialized packages depending on your needs:

• talker: The core Dart package for logging and error handling.
• talker_flutter: Flutter-specific extensions including colored logs, a logs list screen, UI error alerts, and route observers.
• talker_logger: A customizable pretty logger.
• Integration Loggers:
  • talker_dio_logger: For dio HTTP calls.
  • talker_bloc_logger: For bloc state management.
  • talker_riverpod_logger: For riverpod state management.
  • talker_chopper_logger: For chopper HTTP calls.
  • talker_http_logger: For the http package.
  • talker_grpc_logger: For grpc calls.

Use talker_riverpod_logger to log Riverpod event calls and state emissions.

1. Add the dependency:

dependencies:
  talker_riverpod_logger: ^5.1.20

2. Register the TalkerRiverpodObserver in your ProviderScope (for Flutter apps) or ProviderContainer (for pure Dart apps).

import 'package:talker_riverpod_logger/talker_riverpod_logger.dart';

// For Flutter apps
runApp(
  ProviderScope(
    observers: [
      TalkerRiverpodObserver(),
    ],
    child: MyApp(),
  )
);

// For pure Dart apps
final container = ProviderContainer(
  observers: [
    TalkerRiverpodObserver(),
  ],
);

To ensure HTTP logs are integrated into your existing centralized logging system, pass your existing Talker instance to the talker parameter of TalkerChopperLogger.

final talker = Talker();
final client = ChopperClient(
  /// ... other chopper settings
  interceptors: [
    TalkerChopperLogger(
      talker: talker,
      settings: const TalkerChopperLoggerSettings(
        printRequestHeaders: true,
        printResponseHeaders: true,
        printResponseMessage: true,
      ),
    ),
  ],
);

To enable logging for all BLoCs in your application, assign a new instance of TalkerBlocObserver to the Bloc.observer field.

import 'package:talker_bloc_logger/talker_bloc_logger.dart';

Bloc.observer = TalkerBlocObserver();

Add talker_chopper_logger to your pubspec.yaml dependencies to use it with Chopper clients.

dependencies:
  talker_chopper_logger: ^5.1.20

The example project demonstrates how to use riverpod in a pure Dart environment (without Flutter) and how to handle asynchronous provider dependencies.

To run the example, you must first configure your Marvel API credentials in models.dart and then generate the necessary build files.

// 1. Update models.dart with your Marvel API credentials
final hash = md5
        .convert(
          utf8.encode(
            '$timestamp${"<your private key>"}${"<your public key>"}',
          ),
        )
        .toString();

final result = await _client.get<Map<String, Object?>>(
      'http://gateway.marvel.com/v1/public/comics',
      queryParameters: <String, Object?>{
        'ts': timestamp,
        'apikey': "<your public key>",
        'hash': hash,
      },
    );

// 2. Generate files
dart run build_runner build --delete-conflicting-outputs

Add talker_dio_logger to your pubspec.yaml dependencies to use it as a lightweight and customizable logger for the dio HTTP client.

dependencies:
  talker_dio_logger: ^5.1.20

Use TalkerRouteObserver to record page transitions in your application. It is compatible with standard Flutter Navigator and popular routing packages like auto_route and go_router.

// Standard Navigator
final talker = Talker();
MaterialApp(
  navigatorObservers: [
    TalkerRouteObserver(talker),
  ],
)

// go_router
final talker = Talker();
GoRouter(
  observers: [TalkerRouteObserver(talker)],
)

// auto_route v7
final talker = Talker();
MaterialApp.router(
  routerConfig: _appRouter.config(
    navigatorObservers: () => [
      TalkerRouteObserver(talker),
    ],
  ),
),