Repository navigation
딜리트 히스토리 부분을 하는 도중 어디가 잘 못 되었는지 찾지 못해 지우고 처음부터 다시할 계획 - #121
Merged
Merged
Conversation
javajigi
approved these changes
Jan 6, 2019
| this(0L, subject, comment, writer); | ||
| } | ||
|
|
||
| public Issue(long id, String subject, String content, User writer) { |
Contributor
There was a problem hiding this comment.
생성자가 너무 많은데 꼭 필요한 생성자만 추가할 수 없을까?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
이번에 이슈관리를 만들며, ajax, deleteHistory를 이용한 db전체를 삭제 하지 않고 화면에 보여지지 않게만 만드는 작업, api 이슈 컨트롤러 등을 만들면서 굉장히 많은 시간을 보냈고, 힘들었던 거 같습니다. 아직도 어려운 부분이 있었지만, 몇번 반복 하고 나니, 이해하지 못하던 부분도 이해하게 되어서 굉장히 좋았던 거 같습니다. 아직 Api Acceptance Test에서 계속 에러가 발생하여 잡지 못하였지만, 시간이 늦어, 내일 다시 찾아볼 생각입니다.