How abdulrahmanhatem911/clean_code_test works
Project type and purpose
• This is a cross-platform Flutter mobile (and desktop/web) application.
• It follows a “clean architecture” style, structuring code into layers: core, features, data/domain/presentation, and uses state management (Cubit), DI (service_locator), network (Dio) + local caching.
File structure
• Top level:
– android / ios / linux / macos / windows / web: platform‐specific runners & configs
– lib: actual Dart code, broken into:
· config (routes, styling, theming)
· core (exports, network helpers, local server stub, translation, utilities, widgets)
· features/posts & features/saved (each: data, domain, presentation)
· services (app observer, cache helper, service locator)
· main.dart / post_app.dart (app bootstrap)
• pubspec.yaml + analysis_options.yaml: dependency and lint config
• test/widget_test.dart: basic widget test
README for additional insights
• A boilerplate Flutter project, no custom architecture doc in README
• Clearest clues about architecture come from file naming and structure