feat: added question comparing side-effect handlers (LaunchedEffect, SideEffect, DisposableEffect). #32
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.
Hi there!
This PR contributes a set of new Android interview questions as part of the Hacktoberfest initiative.
I added a crucial new interview question to the list, focusing on side-effect handlers in Jetpack Compose (LaunchedEffect, SideEffect, and DisposableEffect).
Changes Made
Added a new question: "Compare and contrast LaunchedEffect, SideEffect, and DisposableEffect. Provide a clear use case for each one."
Included a clear, structured answer highlighting the key differences in terms of lifecycle, use cases, and cleanup requirements.
Closes #28
This question is important as it tests a candidate's understanding of how to manage asynchronous logic and lifecycle interactions within the declarative paradigm of Compose. This is a fundamental concept and a common point of confusion for many developers.
Summary by CodeRabbit