Implement Compose Navigation Safe Args #31
Merged
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 refactors the navigation within the application to use Compose Navigation Safe Args. Key changes include:
LeetCodePlusNavGraph
to use the new sealed class destinations and thetoRoute
extension function for argument handling in the WebView screen.LeetCodePlusNavigation
to accept and navigate using the sealed class objects.kotlinx.serialization.json
dependency and the corresponding Kotlin serialization plugin for handling navigation arguments.caller
parameter from theWebViewScreen
composable.Android Doc: https://developer.android.com/guide/navigation/design/type-safety