Skip to content
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

Don't restart Activity stack when there is no deep link #854

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

arkivanov
Copy link
Owner

@arkivanov arkivanov commented Feb 28, 2025

Summary by CodeRabbit

  • Bug Fixes
    • Enhanced deep link processing to ensure that the app triggers a restart only when valid deep link data is available, improving stability and preventing unintended behavior.

Copy link

coderabbitai bot commented Feb 28, 2025

Walkthrough

The changes update the handleDeepLink function in DeeplinkUtils.kt by introducing a local variable to hold the intent's URI data. The conditional check now ensures that deep link processing only occurs when valid intent data exists and the restart check returns true. The deep link assignment is also updated to use this local variable, aligning the processing logic with the presence of valid intent data.

Changes

File Path Change Summary
decompose/src/androidMain/kotlin/.../DeeplinkUtils.kt Updated handleDeepLink to capture intent data in a local variable, modified the condition to require non-null intent data along with a positive restart check, and updated the deep link assignment accordingly.

Sequence Diagram(s)

sequenceDiagram
    participant I as Intent
    participant D as DeeplinkUtils
    participant R as RestartChecker

    I->>D: Pass intent
    D->>D: Extract intentData from intent
    alt intentData exists
        D->>R: Check restartIfNeeded()
        alt Restart needed
            R-->>D: Returns true
            D->>D: Assign deepLink from intentData and process deep link
        else Restart not needed
            D->>D: Skip deep link processing
        end
    else No intentData
        D->>D: Skip deep link processing
    end
Loading

Poem

I’m a bunny hopping with delight,
Updated code shining bright at night.
Intent data now well in view,
With checks so clear and logic true.
Leap ahead, the changes cheer—
CodeRabbit sings a joyful "hear, hear!"
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
decompose/src/androidMain/kotlin/com/arkivanov/decompose/DeeplinkUtils.kt (1)

11-46: Consider updating the function documentation

While the implementation changes are good, the function documentation hasn't been updated to reflect the new behavior. Consider updating the documentation to mention that the Activity stack restart only happens when there's a deep link.

 * It is strongly recommended to always use the `standard` (default)
 * [launchMode](https://developer.android.com/guide/components/activities/tasks-and-back-stack#TaskLaunchModes)
 * for the [Activity] when handling deep links. This function takes care of
-* restarting the [Activity] task and finishing this [Activity] if needed,
+* restarting the [Activity] task and finishing this [Activity] if needed (only when a deep link is present),
 * in which case the returned value is `null`.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bb551a9 and bc1c113.

📒 Files selected for processing (1)
  • decompose/src/androidMain/kotlin/com/arkivanov/decompose/DeeplinkUtils.kt (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Build on Linux
  • GitHub Check: Build on macOS
🔇 Additional comments (2)
decompose/src/androidMain/kotlin/com/arkivanov/decompose/DeeplinkUtils.kt (2)

51-53: Improvement to prevent unnecessary Activity stack restarts

This change ensures that the Activity stack is only restarted when there's actual deep link data available, which is a good optimization.

By storing the intent data in a local variable and only restarting when both intentData != null and restartIfNeeded() is true, unnecessary restarts are avoided when no deep link exists.


59-59: Consistent use of the local variable

The code now properly uses the stored intentData variable rather than accessing intent.data again, which is more consistent and slightly more efficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant