refactor(di): Introduce @ProcessLifecycle qualifier for di #3978
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 the
@ProcessLifecyclequalifier to disambiguateLifecycleandLifecycleOwnerdependency injections. This resolves an issue where@ActivityScopedbindings inMeshServiceClientwere conflicting with the application-wideProcessLifecycleOwnerprovider inApplicationModule.@ProcessLifecyclequalifier annotation in thecore.dipackage.ApplicationModuleto provideLifecycleOwnerandLifecycleusing the@ProcessLifecyclequalifier.Lifecycledependencies inRadioInterfaceService,UsbRepository,NodeRepository, andBluetoothRepositorywith@ProcessLifecycleto ensure they receive the application-level lifecycle.MeshServiceClientto inject@ActivityContext Contextinstead ofActivity, resolving the scope conflict and simplifying the code.