-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat - 배너 정보 불러오기 #197
feat - 배너 정보 불러오기 #197
Conversation
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.
깔끔하게 잘 작성해주신 것 같아요 👍
코멘트 하나만 남겼는데 확인 부탁드립니다!
package sopt.org.hmh.domain.banner.repository; | ||
|
||
import sopt.org.hmh.domain.banner.Banner; | ||
|
||
import java.util.Optional; | ||
|
||
public interface BannerRepository { | ||
Optional<Banner> findTopByOrderByIdAsc(); | ||
} |
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.
P4. Banner 엔티티는 Jpa외에 복잡한 쿼리를 사용할 일이 없을 것 같아 JpaRepository 하나만 있는게 코드 복잡도 측면에서 더 좋을 것 같은데 어떠신가요?
저는 보통 복잡한 쿼리가 필요하여 Querydsl 사용시에 이렇게 나누는 편이라 복잡한 쿼리가 필요없다면 하나만 유지해도 좋을 것 같아요!
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.
좋은 생각입니당! 빠른 코리 감사드려요
Related issue 🚀
Work Description 💚
PR 참고 사항