-
Notifications
You must be signed in to change notification settings - Fork 0
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
Harry #8
base: review/kotlin
Are you sure you want to change the base?
Harry #8
Conversation
DB까지 다 연결시켜버리는 해리 클라스... |
) { | ||
|
||
@PostMapping | ||
fun createBoard(@RequestBody boardRequest: BoardRequest, @RequestParam name:String):String { |
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.
컨트롤러에서 모든 로직을 처리하는 것은 아름답지 않네요
Service 쪽으로 로직을 옮기는게 맞는 것 같습니다
|
||
class UserJoinRequest ( | ||
@JsonProperty("name") | ||
val name: String |
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.
프로젝트소스에서도 이런거를 많이봤는데 변수 이름이 같은데 @JsonProperty("name")
를 어노테이션 하는거는 코딩 스타일 인가요? 궁금!
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.
@DongHyukki 넹 스타일의 차이인 것 같습니다. 나중에 프로퍼티 이름이 변경되더라도 Request key가 같아야하는 경우가 있을 수도 있다고 생각해서 저는 다 달아주는 편이에요~
No description provided.