-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue #296 Dispose NodeConnector intake in onDestroy #297
Open
LachlanMcKee
wants to merge
1
commit into
bumble-tech:1.x
Choose a base branch
from
LachlanMcKee:issue-296-dispose-nodeconnector-intake
base: 1.x
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,6 +5,7 @@ import com.bumble.appyx.core.lifecycle.subscribe | |
import com.jakewharton.rxrelay2.PublishRelay | ||
import com.jakewharton.rxrelay2.Relay | ||
import io.reactivex.Observer | ||
import io.reactivex.disposables.Disposable | ||
|
||
class NodeConnector<Input, Output>( | ||
override val input: Relay<Input> = PublishRelay.create(), | ||
|
@@ -15,6 +16,7 @@ class NodeConnector<Input, Output>( | |
private val exhaust: Relay<Output> = PublishRelay.create() | ||
private var isFlushed = false | ||
private val outputCache = mutableListOf<Output>() | ||
private var intakeDisposable: Disposable? = null | ||
|
||
override val output: Relay<Output> = object : Relay<Output>() { | ||
|
||
|
@@ -31,7 +33,7 @@ class NodeConnector<Input, Output>( | |
} | ||
|
||
override fun onCreate(lifecycle: Lifecycle) { | ||
lifecycle.subscribe(onCreate = { flushOutputCache() }) | ||
lifecycle.subscribe(onCreate = { flushOutputCache() }, onDestroy = { intakeDisposable?.dispose() }) | ||
} | ||
|
||
private val cacheSubscription = intake.subscribe { | ||
|
@@ -55,7 +57,7 @@ class NodeConnector<Input, Output>( | |
} | ||
|
||
private fun switchToExhaust() { | ||
intake.subscribe { exhaust.accept(it) } | ||
intakeDisposable = intake.subscribe { exhaust.accept(it) } | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. makes sense |
||
cacheSubscription.dispose() | ||
} | ||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly we should log an error, or raise an exception if input/output is invoked after
onDestroy
is called, rather than just swallowing silently?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can't skip
onCreate
callback.androidx.lifecycle.LifecycleRegistry.moveToState
forbids going from initialised state to destroyed.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry, I wasn't talking about lifecycles here @CherryPerry. I meant if someone called
input.accept
/output.accept
after onDestroy for the node was called.In this case the output event would be ignored, but the input event would not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO do not see it as a problem that we should take care of, swallowing is OK for me.