-
Notifications
You must be signed in to change notification settings - Fork 11
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
ALTAPPS-1323: Shared research analytic logging issue #1145
ALTAPPS-1323: Shared research analytic logging issue #1145
Conversation
…neActionDispatcherConfig and not bound to analytic.
...java/org/hyperskill/app/android/stage_implementation/fragment/StageImplementationFragment.kt
Outdated
Show resolved
Hide resolved
.flushEvents(eventsToFlush, isAuthorized) | ||
.onFailure { | ||
mutex.withLock { | ||
hyperskillCacheDataSource.logEvents(eventsToFlush) |
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.
I suppose that there is a case where the current user profile can be changed between logEvent
, and old analytic events can revert to being associated with the previous user profile.
However, it is not so critical right now.
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.
@ivan-magda
Yes, you are right. Good point to think about.
…ytic-logging-issue
YouTrack Issues:
ALTAPPS-1323
Checklist
Before Code Review:
Description
AnalyticActionDispatcher
toCompletableCoroutineActionDispatcher
and remove analytic reference;CompletableCoroutineActionDispatcherTest
;AnalyticHyperskillRepositoryTest
.