https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hiring-french
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
s

Stefan Kanev

12/24/2019, 2:11 PM
not necessarily kotlin specific, but let's give it a try: I'm using Jetpack navigation to navigate between two fragments. One is a list of things, the other one shows a specific thing. On the list I'm getting an
Observable<[Thing]>
, and I'd really like to pass a
Observable<Thing>
to the second fragment. However, I cannot figure out how. I have the list observable in the first fragment's view model and my intuition is that when making the transition, there should be a way to prepare the view model for the second fragment and then it can find it via
ViewModelProvider
. Can't figure out how to do it, though. Maybe there's a totally different way. Any clues?
a

Anastasia Finogenova

12/24/2019, 3:26 PM
Your "intuition" is correct you can share a view model . If using navigation you can share viewmodel for a part of your graph out of the box. https://stackoverflow.com/questions/55137338/android-navigation-component-with-shared-view-models The key is this should be the same instance of the view model. You can always pass your data as arguments too
s

Stefan Kanev

12/24/2019, 7:37 PM
thanks. is it possible, though, to be a bit more fine grained? Fragment A has View Model A, it knows it opens Fragment B and has the data Fragment B needs. I'd rather have View Model B (so fragment B is reusable), but I'd like fragment A to prepare it before it opens Fragment B. As far as I can tell it's possible if I put fragment B in a separate Nav Graph, but not sure if I can do it when they are in the same graph
a

Anastasia Finogenova

12/24/2019, 8:55 PM
One fragment can have multiple view models. Fragment B can have two instances view model A and view model B but of you want to avoid references to viewmodel A from fragment B whatsoever then you have to pass the data to fragment B to be used 🤷
s

Stefan Kanev

12/24/2019, 9:09 PM
sure, but the data is an Observable here and I cannot pass it through args (since it's not serializable)
I guess the fundamental question is how do I pass non-serializable data to a fragment
a

Anastasia Finogenova

12/24/2019, 9:10 PM
You can pass the data itself what you need to display (not the observable instance)
But if you need to persist user's modifications of that data the better way is to share some observable instance which can be inside a view model
Your observable holds data so pass that data and not the observable itself
s

Stefan Kanev

12/24/2019, 9:13 PM
I kinda want to pass the observable as the new fragment can make a modification and I'd like to get the new value through the observable, not specifically handle it in the fragment
a

Anastasia Finogenova

12/24/2019, 9:15 PM
Then you have to provide access to that observable from fragment a and fragment b, so that observable can be in a shared viewmodel (I think this is a standard way now) or it can be global/static in a companion object for example (which we had to do once as there was a complicated set up) but the latter doesn't seem clean to me and smells a bit
s

Stefan Kanev

12/24/2019, 9:16 PM
yeah, so ideally, instead of sharing a view model, I'd like to setup a view model in fragment A to be used in fragment B. That way fragment B doesn't know about the view model of fragment A and can be invoked through multiple paths
a

Anastasia Finogenova

12/24/2019, 9:21 PM
I see what you mean, you can do it in reverse , give whichever fragment is invoking fragment b access to view model b to set the data before navigating to fragment b
So if fragment c navigates to fragment b , fragment c will know of viewmodel b but fragment b will not care if it is fragment a or c start destination
s

Stefan Kanev

12/24/2019, 9:22 PM
sure. I tried that, but then
onCleared
doesn't get called
a

Anastasia Finogenova

12/24/2019, 9:22 PM
For that I would create viewmodel b as a Singleton if you are using dagger for example it is pretty easy
s

Stefan Kanev

12/24/2019, 9:23 PM
not using dagger. Unsure I want to use dagger
a

Anastasia Finogenova

12/24/2019, 9:23 PM
Yeah, I have faced a similar issue but the solution was to have a custom method in view model purgeData or something that will be called on Fragment b onViewDesroyed for example to reset
s

Stefan Kanev

12/24/2019, 9:23 PM
got it
just handle clearing in fragment B?
a

Anastasia Finogenova

12/24/2019, 9:24 PM
Yeap, tie it to fragment b lifecycle and clear data in viewmodel
s

Stefan Kanev

12/24/2019, 9:24 PM
I was trying to set up a viewmodelstore in some way before the transition, but failed
a

Anastasia Finogenova

12/24/2019, 9:24 PM
I am not sure it is possible
s

Stefan Kanev

12/24/2019, 9:24 PM
technically if I put fragment B in a new graph, I can obtain it after I call
navigate
and tweak it
but then I need to wrap it in a new graph 😕
anyway, that was very useful. Thank you!
a

Anastasia Finogenova

12/24/2019, 9:26 PM
Why do you think it is necessary for it to be in a new graph?
You should be able to get its instance in the same graph I would expect
s

Stefan Kanev

12/24/2019, 9:27 PM
yeah, but then
onCleared
doesn't get called since the view model store is shared for the whole graph. If I put it in a new graph, the new graph can have its own view model store, and it gets cleared automatically when it gets popped
otherwise, yeah, I can get it in the same graph, but then it needs the manual clearing as you suggested, which I guess will do
a

Anastasia Finogenova

12/24/2019, 9:29 PM
Ok, I see what you mean , that situation smells a bit , I would report a bug and see what Google replies
s

Stefan Kanev

12/24/2019, 9:29 PM
thanks 🙂
z

zhuinden

01/03/2020, 9:07 AM
What a long discussion and no mention of scoping
ViewModel
to a shared
NavGraph
, why is that?
the ViewModelStore should be managed by the NavGraph as you navigate back Navigation should kill it, if it doesn't then Navigation is bugged