Add logger package with debug-only logging wrapper

[Copilot]

Integrates the logger package with automatic suppression in release builds using kDebugMode checks.

Changes

• pubspec.yaml: Added logger: ^2.5.0 dependency
• lib/utils/app_logger.dart: New utility wrapping logger with kDebugMode guards on all methods
• lib/main.dart: Replaced print() calls with AppLogger methods
• test/app_logger_test.dart: Documents expected behavior

Usage

import 'package:stat_iq/utils/app_logger.dart';

AppLogger.d('Debug message');   // Only in debug mode
AppLogger.i('Info message');
AppLogger.w('Warning message');
AppLogger.e('Error occurred', error);

All log calls are wrapped with if (kDebugMode) to ensure zero logging output in production builds.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• dart.dev
  • Triggering command: /usr/bin/curl curl -fsSL REDACTED -o dart-sdk.zip (dns block)
• dl-ssl.google.com
  • Triggering command: /usr/bin/wget wget -qO- REDACTED (dns block)
• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https /usr/lib/apt/methods/https (dns block)
• https://storage.googleapis.com/flutter_infra_release/flutter/a5cb96369ef86c7e85abf5d662a1ca5d89775053/dart-sdk-linux-x64.zip
  • Triggering command: /usr/bin/curl curl --retry 3 --continue-at - --location --output /tmp/flutter/bin/cache/dart-sdk-linux-x64.zip REDACTED (http block)
  • Triggering command: /update-job-proxy /update-job-proxy (http block)
  • Triggering command: /update-job-proxy /update-job-proxy DROP fig basename /usr�� si_-_Surum_1.pemgit@github.com: git est --local mmand GO test -e ity_-_G2.pem bash -store-immutable --file /home/dependabot/dependabot-updater/git.store 3b1b99d2:lib/mai/usr/sbin/iptables home.NfX6MDzWV4 .6/x64/codeql/to-t test (http block)
• https://storage.googleapis.com/flutter_infra_release/releases/stable/linux/flutter_linux_3.24.5-stable.tar.xz
  • Triggering command: /usr/bin/curl curl -L REDACTED -o flutter.tar.xz (http block)
  • Triggering command: /usr/bin/wget wget -q REDACTED -O flutter.tar.xz (http block)
  • Triggering command: /usr/bin/curl curl -fsSL REDACTED -o flutter.tar.xz (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Implement the 'logger' package for logging in the Flutter app.

• Integrate the popular Dart 'logger' package (https://pub.dev/packages/logger) into your app.
• Configure it so that debug logs (e.g., logger.d()) only appear in debug mode when developing on your laptop, but do not appear in production builds (release mode).
• Make sure debug logs are automatically suppressed in release builds by wrapping log statements (or the logger itself) using kDebugMode.
• Do not include sensitive logging or debugging output in production builds.
• Provide an example (e.g., within main.dart or a common utility file) demonstrating how to safely log debug messages in development, but suppress them in production.

This pull request was created as a result of the following prompt from Copilot chat.

Implement the 'logger' package for logging in the Flutter app.

• Integrate the popular Dart 'logger' package (https://pub.dev/packages/logger) into your app.
• Configure it so that debug logs (e.g., logger.d()) only appear in debug mode when developing on your laptop, but do not appear in production builds (release mode).
• Make sure debug logs are automatically suppressed in release builds by wrapping log statements (or the logger itself) using kDebugMode.
• Do not include sensitive logging or debugging output in production builds.
• Provide an example (e.g., within main.dart or a common utility file) demonstrating how to safely log debug messages in development, but suppress them in production.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

This PR integrates the logger package to provide structured, debug-only logging for the Flutter application. The implementation ensures that all log output is automatically suppressed in production builds using kDebugMode guards.

Key Changes:

• Added logger: ^2.5.0 dependency to pubspec.yaml
• Created AppLogger utility class with kDebugMode-guarded wrapper methods around the logger package
• Replaced print() calls in main.dart with appropriate AppLogger methods (debug, info, warning, error)

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
pubspec.yaml	Added logger package dependency (v2.5.0)
lib/utils/app_logger.dart	New utility class providing static logging methods with kDebugMode guards and PrettyPrinter configuration
lib/main.dart	Replaced 13 print() statements with appropriate AppLogger method calls (d/i/w/e) based on log level
test/app_logger_test.dart	Added tests documenting kDebugMode behavior, though tests don't directly test AppLogger class itself

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The test file doesn't actually import or test the AppLogger class that was implemented. These tests only verify kDebugMode behavior without testing the actual AppLogger methods.

Consider importing package:stat_iq/utils/app_logger.dart and testing that the AppLogger methods can be called without throwing exceptions:

import 'package:stat_iq/utils/app_logger.dart';

test('AppLogger methods should not throw in debug mode', () {
  expect(() => AppLogger.d('Test debug message'), returnsNormally);
  expect(() => AppLogger.i('Test info message'), returnsNormally);
  expect(() => AppLogger.w('Test warning'), returnsNormally);
  expect(() => AppLogger.e('Test error', Exception('test')), returnsNormally);
});

This would provide actual test coverage for the AppLogger implementation.