Refactor navigation logic to use a utility function for screen transitions

Author: TechAurelian

lib/screens/home.dart

@@ -12,6 +12,7 @@ import '../common/app_settings.dart';
 import '../common/strings.dart' as strings;
 import '../common/urls.dart' as urls;
 import '../models/counter.dart';
+import '../utils/utils.dart' as utils;
 import '../utils/utils.dart';
 import '../widgets/accept_cancel_dialog.dart';
 import '../widgets/counter_display.dart';
@@ -101,9 +102,9 @@ class _HomeScreenState extends State<HomeScreen> {
 
   /// Navigates to the Settings screen, and refreshes on return.
   Future<void> _loadSettingsScreen() async {
-    await Navigator.push<void>(
+    await utils.navigateToScreen<void>(
       context,
-      MaterialPageRoute(builder: (context) => SettingsScreen(appSettings: _appSettings)),
+      SettingsScreen(appSettings: _appSettings),
     );
     setState(() {
       /* Refresh after returning from Settings screen. */

lib/utils/utils.dart

@@ -15,6 +15,15 @@ String toDecimalString(BuildContext context, int number) {
   return localizations.formatDecimal(number);
 }
 
+/// Navigates to the given screen widget.
+Future<T?> navigateToScreen<T>(BuildContext context, Widget screen) {
+  return Navigator.of(context).push<T>(
+    MaterialPageRoute<T>(
+      builder: (context) => screen,
+    ),
+  );
+}
+
 /// Launches the specified [URL] in the mobile platform, using the default external application.
 ///
 /// Shows an error [SnackBar] if there is no support for launching the URL.