Thanks to visit codestin.com
Credit goes to github.com

Skip to content

fix(android): RootLayout shade cover unexpected delay #10752

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

Merged

Conversation

CatchABus
Copy link
Contributor

@CatchABus CatchABus commented Jun 28, 2025

PR Checklist

What is the current behavior?

During initialization, android RootLayout shade cover animates properties instead of directly setting values.
Also, the exit animation breaks if shade cover color is a gradient as current implementation unsets it.

What is the new behavior?

  • Android RootLayout will set shade cover defaults directly during init step
  • The exit animation will no longer unset color
  • Translate animation values will now be converted to pixels as that's what android expects

Summary by CodeRabbit

  • New Features

    • Improved support for linear gradient backgrounds in shade cover animations on Android.
  • Bug Fixes

    • Enhanced animation smoothness and consistency for shade covers with gradient backgrounds.
  • Style

    • Animations now apply more accurately to device pixel values, resulting in better visual fidelity.

Copy link

coderabbitai bot commented Jun 28, 2025

Walkthrough

The update refactors how linear gradient backgrounds are handled during shade cover animations on Android within the RootLayout class. It separates gradient background logic from color animation, applies pixel conversions for translation values, and updates native view properties directly. All changes are internal and do not affect exported interfaces.

Changes

File(s) Change Summary
packages/core/ui/layouts/root-layout/index.android.ts Refactored shade cover animation logic: separated gradient background handling, applied pixel conversions, updated native view properties, and simplified background color animation logic.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant RootLayout
    participant NativeView

    User->>RootLayout: Trigger shade cover animation
    RootLayout->>NativeView: Apply initial animation state (alpha, scale, translation, rotation)
    RootLayout->>RootLayout: Detect if background is linear gradient
    alt Linear gradient
        RootLayout->>NativeView: Set background image to parsed gradient
        RootLayout->>NativeView: Clear solid background color
    else Solid color
        RootLayout->>NativeView: Clear background image
        RootLayout->>NativeView: Set background color
    end
    RootLayout->>NativeView: Animate properties (translation in device pixels, etc.)
Loading

Possibly related PRs

Suggested reviewers

  • NathanWalker

Poem

In Android’s shade, a gradient flows,
With pixels aligned as the animation goes.
Colors or stripes, the logic is neat—
Now gradients and colors never compete!
Hop, hop, hooray, for backgrounds anew,
The root layout shines with a colorful hue.
🐇🌈

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /.npm/_logs/2025-06-28T18_19_23_919Z-debug-0.log

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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

nx-cloud bot commented Jun 28, 2025

View your CI Pipeline Execution ↗ for commit ccad490.

Command Status Duration Result
nx test apps-automated -c=android ✅ Succeeded 5m 51s View ↗
nx run-many --target=test --configuration=ci --... ✅ Succeeded 3s View ↗

☁️ Nx Cloud last updated this comment at 2025-06-28 18:26:09 UTC

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 (2)
packages/core/ui/layouts/root-layout/index.android.ts (2)

64-77: Well-implemented gradient handling logic!

The separation of gradient backgrounds from color animation correctly addresses the exit animation breakage issue. The mutual exclusivity between backgroundColor and backgroundImage is properly maintained.

Consider using optional chaining for a more concise syntax:

-const isBackgroundGradient = options.color && options.color.startsWith('linear-gradient');
+const isBackgroundGradient = options.color?.startsWith('linear-gradient');

41-116: Consider adding test coverage for the fixes.

While the implementation correctly addresses both the initialization delay and gradient animation issues, the PR checklist indicates no new tests were added. Consider adding unit tests to verify:

  1. Direct property setting during initialization (no animation delay)
  2. Gradient backgrounds are preserved during exit animations
  3. Pixel conversion is applied correctly for translation values

Would you like me to help generate unit tests for these scenarios or open an issue to track this task?

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 242c3ae and ccad490.

📒 Files selected for processing (1)
  • packages/core/ui/layouts/root-layout/index.android.ts (5 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
packages/core/ui/layouts/root-layout/index.android.ts

[error] 64-64: Change to an optional chain.

Unsafe fix: Change to an optional chain.

(lint/complexity/useOptionalChain)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: test-android
  • GitHub Check: test-ios
🔇 Additional comments (2)
packages/core/ui/layouts/root-layout/index.android.ts (2)

41-56: Good fix for the initialization delay issue!

The direct property setting on the native view eliminates the animation during initialization, which correctly addresses the unexpected delay mentioned in the PR objectives. The pixel conversion for translation values ensures proper device-independent rendering.


103-116: Clean refactoring of the animation set logic!

The conditional array sizing and simplified background color animator logic improve code clarity. The consistent use of layout.toDevicePixels for translation values matches the initialization logic.

@NathanWalker NathanWalker merged commit 2da4170 into NativeScript:main Jun 28, 2025
4 checks passed
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.

2 participants