-
Notifications
You must be signed in to change notification settings - Fork 0
dev <- main #163
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
dev <- main #163
Conversation
…Spring Boot launch
Summary of ChangesHello @Finefinee, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request primarily focuses on refining the application's error handling and logging infrastructure. It introduces robust file-based logging using Logback, enhances the global exception handler with detailed logging for various error types, and makes error messages more flexible. Additionally, it adjusts the Highlights
Ignored Files
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
이 PR은 SLF4J와 Logback을 사용하여 로깅 기능을 도입하고, 예외 처리에 로깅을 포함하도록 리팩토링했습니다. 또한 Member 엔티티의 email 필드를 선택 사항으로 변경했습니다. 전반적으로 좋은 변경 사항이지만, 몇 가지 개선점을 제안합니다.
주요 피드백:
logback-spring.xml에서 로그 경로가 하드코딩되어 있어 이식성이 떨어질 수 있습니다. 상대 경로를 사용하도록 수정하는 것이 좋습니다.GlobalExceptionHandler.java의 에러 로그 메시지에서 이모지를 제거하여 로그 파서와의 호환성 문제를 방지하는 것이 좋습니다.
자세한 내용은 각 파일의 개별 코멘트를 확인해주세요.
| @@ -0,0 +1,20 @@ | |||
| <?xml version="1.0" encoding="UTF-8"?> | |||
| <configuration> | |||
| <property name="LOG_PATH" value="/home/ubuntu/logs"/> | |||
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.
| // 그 외 모든 예외 처리 | ||
| @ExceptionHandler(Exception.class) | ||
| public ResponseEntity<ApiResponse<Void>> handleException(Exception e) { | ||
| log.error("🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 Unhandled Exception occurred: ", e); |
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.
No description provided.