New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

hexagonal architecture 구조로 잡아보시는건 어떠할까요? #8

Open

sean5940 opened this issue Jan 22, 2022 · 2 comments

sean5940 commented Jan 22, 2022 •

edited

Loading

이런식으로 구조 잡는건 어떠할까요?
요런 구조면, application의 주요한 비즈니스 로직을 단위 테스트하기 쉽고,
테스트 전략을 세우는 것과 어떤 코드를 테스트를 만들고 안만들지 선별하기도 수월하더라구요.

lib
- src
  - main.dart
  - adapters
    - network
      - rest
      - graphql
      - ...
    - persistance
      - hive
      - shared_preferences
      - get_storeage
      - ....
    - presentation (getx 기준으로 잡았는데, 상황에 따라 다른 구조로 잡아도 될거 같아요)
      - common
      - module
        
        account
        
        bindings
        
        controller
        
        view
        
        widget
        
        service
      - getx_service
      - routes
  - applications
    - account
      - application
        
        port
        
        in
        
        out
        
        service
      - domain
      - common or util (account에서 공통으로 사용되는 class 모음)
    - ...
  - common (해당 구조에서 공통으로 사용하는 class 모음)
    - logger
    - error

Contributor

Jay-flow commented Jan 22, 2022

@SungilJung Thank you for your advice. I'll think about what you said and tell you again :)

Author

sean5940 commented Jan 23, 2022 •

edited

Loading

@Jay-flow
https://youtu.be/IHrZD3vxYB0
It will be helpful if you watch this video and refer to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment