Update README.md

README.md

@@ -437,93 +437,7 @@ This should be best suited for the size of the project.
 
 ### Should Providers and UI always be placed in separate files?
 
-I don't think so. Look at this for example.
-```dart
-@riverpod
-class Sort extends _$Sort {
-  @override
-  ScoreType? build() => null;
-
-  void update(ScoreType type) => state = type;
-}
-
-@riverpod
-Future<List<Package>> sortedPackages(SortedPackagesRef ref,
-    {required String search}) async {
-  final packages = await ref.watch(packagesProvider(search: search).future);
-  final sort = ref.watch(sortProvider);
-
-  return sort == null
-      ? List.of(packages)
-      : packages.sortedByCompare(
-          (package) => sort.getValue(package.score), (a, b) => b.compareTo(a));
-}
-
-// ...PackagesPage
-
-class _SortPanel extends ConsumerWidget {
-  const _SortPanel();
-
-  @override
-  Widget build(BuildContext context, WidgetRef ref) {
-    final l10n = ref.watch(l10nProvider);
-    final sort = ref.watch(sortProvider);
-
-    return Column(
-      crossAxisAlignment: CrossAxisAlignment.start,
-      children: [
-        Text(
-          l10n.packagesPage.sortPackages,
-          style: Theme.of(context).textTheme.labelLarge,
-        ),
-        const Gap(8),
-        for (var score in ScoreType.values)
-          ScoreRadioTile(
-            type: score,
-            groupeType: sort,
-            onTap: (type) => sort == type
-                ? ref.invalidate(sortProvider)
-                : ref.read(sortProvider.notifier).update(type),
-          ),
-      ],
-    );
-  }
-}
-
-class _PackageItems extends ConsumerWidget {
-  const _PackageItems({required this.searchText});
-
-  final String searchText;
-
-  @override
-  Widget build(BuildContext context, WidgetRef ref) {
-    final packages = ref.watch(sortedPackagesProvider(search: searchText));
-    final l10n = ref.watch(l10nProvider);
-
-    return switch (packages) {
-      AsyncData(:final value) => value.isEmpty
-          ? SingleChildScrollView(
-              child: EmptyImage(text: l10n.packagesPage.packageNotFound),
-            )
-          : RefreshIndicator(
-              onRefresh: () => ref.refresh(packagesProvider(
-                search: searchText,
-                debounce: false,
-              ).future),
-              child: ListView.separated(
-                separatorBuilder: (_, __) => const Divider(),
-                itemCount: value.length,
-                itemBuilder: (_, int i) => PackageItem(value[i]),
-              ),
-            ),
-      AsyncError(:final error) => Text(error.toString()),
-      _ => const Center(child: CircularProgressIndicator()),
-    };
-  }
-}
-```
-
-This is the codes of [packages_page.dart](https://github.com/natsuk4ze/npm/blob/master/lib/features/packages/packages_page.dart), which is a UI file, but with providers.
+I don't think so. Look at [packages_page.dart](https://github.com/natsuk4ze/npm/blob/master/lib/features/packages/packages_page.dart) for example, which is a UI file, but with providers.
 My basic idea is **put things close to each other in close proximity.**
 I don't think it's necessary to put them in a data (domain) layer file, since all the providers here are only for this *packages page*.
 However, this should also be changed depending on the project. If it is a large project, these providers might be placed in a file called ~controller. But this seems a bit far from the declarative UI philosophy.