chore: fix and format using melos
This commit is contained in:
@@ -18,14 +18,14 @@ import 'package:flutter/widgets.dart';
|
||||
import 'package:flutter_bloc/flutter_bloc.dart';
|
||||
|
||||
/// {@template multi_provider}
|
||||
/// Merges [MultiRepositoryProvider] and [MultiBlocProvider] widgets into
|
||||
/// Merges [MultiRepositoryProvider] and [MultiBlocProvider] widgets into
|
||||
/// one widget tree.
|
||||
///
|
||||
/// [MultiProvider] improves the readability and eliminates the need
|
||||
/// to nest multiple providers.
|
||||
///
|
||||
/// By using [MultiProvider] we can go from:
|
||||
///
|
||||
///
|
||||
/// ```dart
|
||||
/// MultiRepositoryProvider(
|
||||
/// providers: [
|
||||
@@ -69,7 +69,7 @@ import 'package:flutter_bloc/flutter_bloc.dart';
|
||||
/// )
|
||||
/// ```
|
||||
///
|
||||
/// [MultiProvider] converts the [RepositoryProvider] and [BlocProvider] lists
|
||||
/// [MultiProvider] converts the [RepositoryProvider] and [BlocProvider] lists
|
||||
/// into a tree of nested provider widgets.
|
||||
/// As a result, the only advantage of using [MultiProvider] is
|
||||
/// improved readability due to the reduction in nesting and boilerplate.
|
||||
|
||||
Reference in New Issue
Block a user