-
Notifications
You must be signed in to change notification settings - Fork 1
swagger 문서 작업 #51
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.
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
base: develop
Are you sure you want to change the base?
swagger 문서 작업 #51
Conversation
user/serializer.py
Outdated
| class SignupRequestBodySerializer(UserSerializer, UserProfileSerializer): | ||
| def __init__(self): | ||
| super(SignupRequestBodySerializer, self).__init__() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
갠적으로 모델 시리얼라이저 를 다중상속 하지말고, 번거롭더라도 request json필드 그대로 시리얼라이저 그대로 가는걸 선호합니다만,
궁금한게 이렇게 시리얼라이저 적용하고나서 생성되는 Swagger 문서에 RequestBody의 필드가 View 로직에서 request.data 로 받는 필드와 정확하게 매칭이 되나요?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ginza/settings/local.py
Outdated
| CORS_ALLOW_ALL_ORIGINS = True | ||
|
|
||
| CORS_ALLOW_CREDENTIALS = True |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CORS관련 설정이 추가된 사유가 뭘까요?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
이거 중간에 카카오 인증쪽 호스트 접속 하는 과정에서 cors 때문에 추가하신듯 한데,
React에서 proxy 설정을 지정하면 이슈가 없을듯 해서 일단 이부분은 원복 부탁드릴께요

Check List
PR 개요
주요 작업사항