live-event
[ACTIVE] Lifecycle-aware wrapper over EventEmitter, for modelling one-off events. (by Zhuinden)
SingleLiveEvent-EventWrapper-LiveData
By nirmaljeffrey
| live-event | SingleLiveEvent-EventWrapper-LiveData | |
|---|---|---|
| 7 | 1 | |
| 63 | 7 | |
| - | - | |
| 3.3 | 0.0 | |
| 5 months ago | over 4 years ago | |
| Kotlin | Java | |
| Apache License 2.0 | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
live-event
Posts with mentions or reviews of live-event.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-07.
-
How to make kotlin library
For Android-specific code, you need slightly different configuration of the maven-publish plugin, but I use it in this repo https://github.com/Zhuinden/live-event
-
Sending View Model Events to the UI (is this how people are handling Navigation and Snackbars now?)
For events, I use https://github.com/Zhuinden/event-emitter with https://github.com/Zhuinden/live-event
-
What's the proper way of accessing a Composable function from a non-composable one?
ok technically I think last time I even used https://github.com/Zhuinden/live-event because I have lifecycle support via fragments in Composables
-
What do you use except SingleLiveEvent for one time actions in MVI/MVVM?
I've been using this: https://github.com/Zhuinden/live-event
-
LiveData vs SharedFlow and StateFlow in MVVM and MVI Architecture
Well I've been using this which is merely a lifecycle-aware wrapper over this, if you're in Kotlin and you are using coroutine stuff then you can also use Channel(UNLIMITED) with receiveAsFlow()
-
SharedFlow asLiveData replays emissions - expected?
I originally wrote https://github.com/Zhuinden/live-event but you can use Channel(UNLIMITED).asFlow()
-
Migrating from LiveData to Kotlin’s Flow
I wrote https://github.com/Zhuinden/live-event/ to make it easy but for some reason nobody uses it, they instead copy-paste LiveData> / SingleLiveData from Google even though it's effectively a hack
SingleLiveEvent-EventWrapper-LiveData
Posts with mentions or reviews of SingleLiveEvent-EventWrapper-LiveData.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-29.
What are some alternatives?
When comparing live-event and SingleLiveEvent-EventWrapper-LiveData you can also consider the following projects:
event-emitter - [ACTIVE] The event emitter allows you to register multiple observers, but enqueue events while there are no observers.
jetpack-navigation-ftue-sample - [DEMO] Sample code to display "First-Time User Experience" in a Single-Activity app using Jetpack-Navigation, NavGraphs, Dagger, SavedStateHandle, Hilt, and EventEmitter - based on the FTUE example code in simple-stack-tutorials, but originally described by Google.
simple-stack-ftue-sample - [DEMO] Sample code to display "First-Time User Experience" in a Single-Activity app using Simple-Stack, based on the "Conditional Navigation" section by Google.