How codernamedhendrick/solar_icons works
Main Architectural Components
a. Core Library (“solar_icons” package)
– Entry point: lib/solar_icons.dart
– Source files: lib/src/solar_icons_data.dart (raw vector or font glyph data), lib/src/solar_icons_{style}.dart (bold, broken, outline, etc.).
– Configuration: pubspec.yaml (defines package name, version, dependencies).
b. Example Application
– Multi-platform Flutter project under /example
– Platform directories: android/, ios/, web/, linux/, macos/, windows/
– Shared Dart code: example/lib/main.dart
– Example pubspec.yaml (pulls in solar_icons as a path or hosted dependency)
c. CI/CD & Quality
– GitHub Actions workflow (/.github/workflows/test.yaml) running tests & code coverage.
– Codecov integration (badge in README).
d. Tests
– Example widget tests (example/test/widget_test.dart)
Interactions and Data Flows
– Consumer App (example or any Flutter app)
→ imports “solar_icons” library
→ Flutter framework renders IconData via Skia/engine on each target platform
– CI System
→ On push/PR, GitHub Actions checks out code → runs flutter test on both package and example → reports to Codecov → updates badges.
Architectural Patterns & Design Principles
– Separation of Concerns:
• Core library (pure Dart) is platform-agnostic.
• Example app isolates platform integration in each folder (standard Flutter structure).
– Modular Design:
• Data (vector paths) is separated from API (IconData constants).
– CI as code: workflow YAML defines automated tests.
Elements
– Core Library (Dart package)
– Example Flutter App
– Flutter Framework & Engine
– Target Platforms (Android, iOS, Web, macOS, Linux, Windows)
– CI/CD (GitHub Actions)
– Codecov / Test Suite
– App → imports → Library
– Library → exposes → IconData
– App/Framework → renders → Skia/Engine → platforms
– GitHub Actions → runs → Tests → publishes → Coverage report
• Labels:
– APIs (IconData constants)
– Data artifacts (vector paths or font glyphs)
– Workflows (test.yaml)