-
Notifications
You must be signed in to change notification settings - Fork 0
[UNI-73] refactor : 길찾기 로직 응답형태 리팩토링 #25
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
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.
getCenter 메서드를 Route 내부로 넣어두는건 어떻게 생각하시는지 궁금합니다 !!
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.
오 그게 훨씬 더 좋은 방향인것 같습니다! 반영한 뒤 머지하겠습니다!!
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.
생각해보니 getCenter를 Route 내부에서 정의하게되면 메서드가
이렇게 될텐데, 만약 Lazy loading 상태인(fetch join을 하지 않은) Route에서 getCenter를 호출할 경우 추가 쿼리문이 나갈 위험성이 있을것 같습니다.
게다가 현재 Route에서 node1, node2가 (fetch = LAZY) 로 선언되어있기 때문에 더더욱 추가 쿼리문의 가능성이 높아보입니다.
의견 남겨주시면 확인 후 머지하겠습니다!
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.
말씀주신 것에 동감합니다!
그래서 전 항상 기능 개발할때 "해당 기능에서 발생하는 쿼리도 의도대로 잘 동작하는지" 까지도 고려해서 기능개발하는 게 좋다고 생각하는데요! 어떻게 생각하시는지 궁금합니다!
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.
네 좋습니다! 의도대로 동작하는지 스스로도 점검하고, 앞으로 코드리뷰할때도 꼼꼼하게 보겠습니다!