Project Strategy

Stack

Frontend

• React
• TypeScript

Backend

• Spring boot

Datebase

• mySQL

Crawling

• Python

Library

Date Visualization

• billboard.js
• d3.js

Styling

• styled-components

Design Component

• Ant Design
• medium-zoom

API

• Naver Search > Movie API
• KOBIS
• TMDb
• Youtube Data API

Branch 전략

저희는 Branch 전략으로 git flow를 변형해서 사용하려합니다.

frontend와 backend에서 각각 본인의 branch( ex){github_id}-frontend(or backend) )를 새로 파서 본인 branch에서 작업 후 기능 구현이 완성될 때마다 frontend로 pull request를 날려 conflict가 없으면 본인이 merge하고 있으면 같이 리뷰하여 conflict resolve한 후 merge하는 방식으로 진행합니다.

Git Branch Tree

• master don't use this branch
• frontend frontend orphan branch
  • dl0312-frontend
    • dl0312-frontend/{issue_number}
  • qlqnf16-frontend
    • qlqnf16-frontend/{issue_number}
• backend backend orphan branch
  • zerobell-lee-backend
    • zerobell-lee-backend/{issue_number}

Commit message template

commit message template은 다음과 같습니다. 참고

• feat: (new feature for the user, not a new feature for build script)
• fix: (bug fix for the user, not a fix to a build script)
• docs: (changes to the documentation)
• style: (formatting, missing semi colons, etc; no production code change)
• refactor: (refactoring production code, eg. renaming a variable)
• test: (adding missing tests, refactoring tests; no production code change)
• chore: (updating grunt tasks etc; no production code change)