Skip to content
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

refactor: be course 응답 dto #167

Closed
pushedrumex opened this issue Dec 1, 2022 · 0 comments
Closed

refactor: be course 응답 dto #167

pushedrumex opened this issue Dec 1, 2022 · 0 comments
Assignees
@pushedrumex
Labels
backend refactor
Milestone
4주차

Comments

@pushedrumex
Copy link
Member

리팩토링 배경

현재는 dto를 사용하지 않고 {statusCode: , data : {}}로 응답을 하고 있다. 응답 처리를 용이하게하고 dto와 entity의 역할을 분리하기 위해 응답 dto와 entity를 구성하여 응답하는 방식을 사용한다.

기대효과

  1. 응답 처리 용이
  2. 추후 Swagger 적용할 때 편리

체크리스트

각 end point에 대한 응답 dto와 entity를 활용하여 응답을 구성한다.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pushedrumex pushedrumex

Labels
backend refactor
Projects
None yet
Milestone
4주차
Development

No branches or pull requests
1 participant
@pushedrumex