Skip to content

Commit 53fe8a1

Browse files
authored
Update README.md
1 parent 6bc5a29 commit 53fe8a1

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

README.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@
1313
![badge][badge-jvm]
1414
![badge][badge-js]
1515
![badge][badge-js-ir]
16+
![badge][badge-wasm]
1617
![badge][badge-nodejs]
1718
![badge][badge-linux]
1819
![badge][badge-windows]
@@ -134,6 +135,7 @@ bus
134135

135136
- `jvm` / `android`.
136137
- `js` (`IR`).
138+
- `wasmJs`.
137139
- `Darwin` targets:
138140
- `iosArm64`, `iosX64`, `iosSimulatorArm64`.
139141
- `watchosArm32`, `watchosArm64`, `watchosX64`, `watchosSimulatorArm64`, `watchosDeviceArm64`.
@@ -149,31 +151,31 @@ bus
149151
an Android app using Compose UI to show how to use the library.
150152
It has two nested navigation graphs: `Register` and `Home`.
151153

152-
- In `Register`, we have 3 steps (3 screens) to allow user to input their information, step
154+
- In `Register`, we have 3 steps (3 screens) to allow the user to input their information, step
153155
by
154156
step.
155157
- A `RegisterSharedViewModel` (bound to `Register` navigation graph scope) is used
156158
to hold the whole state of the registration process.
157-
It observes events from the `ChannelEventBus` and update the state accordingly.
159+
It observes events from the `ChannelEventBus` and updates the state accordingly.
158160

159-
- Each step screen has a `ViewModel` to hold the state of the screen, and will send events to
161+
- Each step screen has a `ViewModel` to hold the state of the screen and will send events to
160162
the `ChannelEventBus`,
161163
then the `RegisterSharedViewModel` will receive those events and update the state.
162164

163-
- In `Home` nav graph, we have 2 screens: `Home` and `Detail`.
164-
- `Home` screen has a `HomeViewModel` to hold the results received from the `Detail` screen.
165+
- In the `Home` nav graph, we have 2 screens: `Home` and `Detail`.
166+
- The `Home` screen has a `HomeViewModel` to hold the results received from the `Detail` screen.
165167
Those result events are sent from the `Detail` screen to the `ChannelEventBus`,
166168
and the `HomeViewModel` will receive those events and update the state.
167169

168-
- `Detail` screen will send events to the `ChannelEventBus` when user clicks on the button.
170+
- The `Detail` screen will send events to the `ChannelEventBus` when the user clicks on the button.
169171
The `HomeViewModel` will receive those events and update the state.
170172

171173
https://github.com/hoc081098/kotlin-channel-event-bus/assets/36917223/80015232-d5b5-4fb2-a779-4e6113ddb8f8
172174

173175
## Roadmap
174176

175-
- [ ] Support more targets: `wasm` (depends on supported targets by `kotlinx.coroutines`).
176-
- [ ] More samples.
177+
- [x] Support more targets: `wasm` (depends on supported targets by `kotlinx.coroutines`) (since [0.1.0](https://github.com/Kotlin-Multiplatform-Foundation/kotlin-channel-event-bus/releases/tag/0.1.0)).
178+
- [x] More samples.
177179
- [ ] More docs.
178180
- [ ] More tests.
179181

0 commit comments

Comments
 (0)