Hey, great article! I observed that you used a LiveData inside your repository; probably inspired by Google's Architecture Guide. But this is an anti-pattern and you should replace the livedata with Kotlin's Flow.
You can read this article for a detailed explanation: proandroiddev.com/no-more-livedata...
Thanks for sharing! I was wondering why we would do that... LiveData (Android dependency) in business logic, seemed weird.
Thank you so much! I'll go through the article and try to make corrections as soon as possible
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey, great article! I observed that you used a LiveData inside your repository; probably inspired by Google's Architecture Guide. But this is an anti-pattern and you should replace the livedata with Kotlin's Flow.
You can read this article for a detailed explanation: proandroiddev.com/no-more-livedata...
Thanks for sharing! I was wondering why we would do that... LiveData (Android dependency) in business logic, seemed weird.
Thank you so much! I'll go through the article and try to make corrections as soon as possible