Does it make sense to back a toggleable component Switch Che kotlinlang #compose

Channels

kotlin-foundation

compose-android

ohio-kotlin-users

kotlin-by-example

sofl-user-group

kotlin-multiplatform-contest

tricity-kotlin-user-group

kotlin-in-action

android-databinding

cincinnati-user-group

fluid-libraries

codemash-precompiler

kotlingforbeginners

jhipster-kotlin

prozis-android-backup

realworldkotlin

graviton-browser

spring-security

domain-driven-design

connect-audit-events

swiss-user-group

effectivekotlin

refactoring-to-kotlin

russian-kotlinasfirst

androidgithubprojects

introduce-yourself

pocketgitclient

effective-kotlin

algolialibraries

lambdaworld_cadiz

intellij-tricks

kotlin-pakistan

navigation-architecture-component

strife-discord-lib

machinelearningbawas

leedskotlinusergroup

stayhungrystayfoolish

kotest-contributors

practical-functional-programming

swagger-gradle-codegen

100daysofkotlin

kotlinultimatechallenge

pattern-matching

kotlinforbeginners

competitive-programming

compose-ui-showcase

competitivecoding

kotlin-data-storage

skia-wasm-interop-temp

java-to-kotlin-refactoring

event21-community-content

androidx-xprocessing

embedded-kotlin

fb-internal-demo

image-processing

myndocs-oauth2-server

kotlintest-devs

beepiz-libraries

kotlinprogrammers

cscenter-course-2016

k2-early-adopters

intellij-plugins

language-proposals

library-development

refreshversions

language-evolution

kotlinx-datetime

framework-elide

compose-desktop

jvm-ir-backend-feedback

android-architecture

100daysofkotlin-2021

github-workflows-kt

python-contributors

squarelibraries

arrow-contributors

codingconventions

getting-started

Title

c

Chris Fillmore

01/21/2022, 12:01 AM

Does it make sense to back a toggleable component (Switch/Checkbox) using a

StateFlow<Boolean>

? Even if there are many such components in a list? (dozens? hundreds?)

Supposing I have such a flow attached to some data, like:

data class MyToggleableData(
  val data: MyData,
  val toggle: MutableStateFlow<Boolean>,
)

I wonder if it makes more sense to just store a Boolean, and update the entire List when there is a state change, like:

val myData: MutableStateFlow<List<Pair<MyData, Boolean>>> = ...

fun toggle(myDataItem: MyData, newState: Boolean) {
  myData.update { list ->
    list.map {
      if (it == myDataItem) it.copy(toggle = newState)
    }
  }
}

Roughly like that

Any advice? Thanks!

a

Adam Powell

01/21/2022, 12:50 AM

you could, but if you're going to make individual objects observable+mutable I think you'd have a better time writing that as

class MyToggleableData(
  val data: MyData,
  toggle: Boolean
) {
  var toggle by mutableStateOf(toggle)
}

➕ 2

c

Chris Fillmore

01/21/2022, 2:44 PM

Ok thanks for the feedback Adam!

4 Views

#compose Join Slack