refactor(concurrent): Introduce SequentialJob to manage service setup #3983
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.
This commit introduces a
SequentialJobclass to ensure that only one service setup operation runs at a time. The new class cancels any previous job before launching a new one.SequentialJobclass to manage a single, cancellable coroutine Job.MeshServiceClientto use the injectedSequentialJobfor handling service connection and disconnection, simplifying its logic.SequentialJobto verify that it cancels previous jobs and can be cancelled itself.kotlinx-coroutines-testfor testing.