How juandpt03/colibreria works
Project type and purpose
• This is a Flutter-based mobile application (“Colibreria”) targeting Android, iOS, Web, Linux, Windows, and macOS.
• It follows Clean Architecture to implement a client for searching and viewing technology books via an external API.
File structure
• Top-level platform folders (android/, ios/, linux/, macos/, windows/, web/) contain the platform-specific shell and build configs.
• lib/ is where all Dart code lives, subdivided into:
• src/core – cross-cutting concerns (config, constants, HTTP client, DI, theme, intl, error handling, utilities).
• src/features – grouped by feature (auth, home, shared), each with domain, data, and presentation subfolders.
• main.dart – app entry point.
• test/ holds unit tests for BLoCs and widgets.
• pubspec.yaml lists Flutter and 3rd-party dependencies (flutter_bloc, dio, get_it, go_router, etc.).
README for additional insights
• The README confirms Clean Architecture layering: presentation (UI & BLoC), domain (use cases & entities), data (models & data sources).
• It mentions key techs: Dio (HTTP), flutter_bloc + hydrated_bloc, go_router (routing), get_it (DI), cached_network_image, share_plus, url_launcher, and intl.
Elements
• Blue for Presentation
• Green for Domain
• Orange for Data
• Gray for Core Services
• Purple for External Systems
• Rounded rectangles for modules (features, core services)
• Clouds for external APIs
Detailed capture of essential architectural elements
• Break out each feature (auth, home, shared) into its own sub-component within each layer.
• Injector setup as the central hub wiring everything.