-
Notifications
You must be signed in to change notification settings - Fork 0
Qa/1.0.0 #114
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
Qa/1.0.0 #114
Conversation
- Firebase Crashlytics KTX 의존성 추가 - `proguard-rules.pro` 파일을 생성하여 Proguard 규칙 추가 - Crashlytics 예외 로깅을 위한 `RecordException` 추가 - Crashlytics 플러그인 및 Google Service 플러그인 추가 - core 모듈의 common-android 생성 및 예외 로깅 추가 - feature 모듈에서 발생한 예외에 대한 예외 로깅 처리 추가 - core 모듈과 common 모듈의 build.gradle 파일 수정 - AndroidManifest.xml 파일 추가 - `consumer-rules.pro` 파일 추가
- 특수문자만을 허용하는 것이 아닌, 알파벳과 숫자 이외의 문자를 허용하도록 수정
Increased the `versionCode` in `build.gradle.kts` from 1 to 2. This signifies an update to the application.
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
@@ -55,7 +54,7 @@ class HomeViewModel @Inject constructor( | |||
.catch { error-> | |||
when(error) { | |||
is UserNotFoundForEmailException, is InvalidTokenException -> postSideEffect(HomeSideEffect.NavigateToLogin) | |||
else -> throw error | |||
else -> error.record() |
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.
앞으로 예외는 이렇게 처리하시면 됩니다.
import timber.log.Timber | ||
|
||
fun Throwable.record() { | ||
recordException(RuntimeException(this)) |
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.
Throwable을 rethrow하는 경우 stack trace에 rethrow한 위치가 남지 않아 RuntimeException으로 감샀습니다. 이러면 throw, rethrow의 stack trace 정보가 모두 남게 됩니다.
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.
변경사항 확인했습니다!
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.
확인했습니다 ~
💡 Issue
🌱 Key changes
QA 3개 처리했습니다.
Exception 발생 시, 로그 캣에 정보가 부족했던 현상 해결했습니다.
예를 들어 HomeViewModel에서 Exception이 발생한 경우 아래 처럼 로그가 나옵니다.
하지만 로그를 보시면 HomeViewModel의 몇번 줄에서 Exception이 발생했는지에 대한 정보를 찾을 수 없습니다.
위 이슈 해결했습니다.
✅ To Reviewers
📸 스크린샷