Fix the error in text.bounds when there is no root canvas

[cptbtptpbcptdtptp]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Summary by CodeRabbit

• Bug Fixes
  • Refined the text component’s display logic to ensure that text elements render consistently under a variety of conditions, resulting in a smoother and more reliable user experience.

[coderabbitai]

Walkthrough

The changes update the Text component's visibility logic by modifying the _isTextNoVisible method to include a check for the existence of the root canvas. Additionally, a new test case has been added to verify accurate bounding box calculations for the Text component when no canvas is provided and after adjusting the UI transform size.

Changes

File(s)	Change Summary
packages/ui/.../Text.ts	Updated the _isTextNoVisible method to include a root canvas existence check, altering the conditional logic for text visibility evaluation.
tests/src/ui/.../Text.test.ts	Added a new "get bounds" test case to verify bounding box calculations for the Text component, including checks on label bounds and UI transform size adjustments.

Sequence Diagram(s)

sequenceDiagram
  participant T as Text Component
  T->>T: _isTextNoVisible()
  alt Root Canvas Missing
    T->>T: Return not visible
  else Root Canvas Exists
    alt OverflowMode is "Truncate" and size.y <= 0
      T->>T: Return not visible
    else
      T->>T: Return visible
    end
  end

Loading

Suggested labels

bug, text

Poem

I'm a rabbit with a code-filled heart,
Hopping through changes, a joyful new start.
The text now checks for a canvas so fine,
And bounds are tested in a test divine.
With gentle hops and a cheerful cheer,
I celebrate these tweaks with a bunny sincere! 🐰💻

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5ab9ce4 and 90c55fc.

📒 Files selected for processing (2)

• packages/ui/src/component/advanced/Text.ts (1 hunks)
• tests/src/ui/Text.test.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: e2e (22.x)

🔇 Additional comments (2)

tests/src/ui/Text.test.ts (1)

45-63: LGTM! Comprehensive test coverage for text bounds.

The test case thoroughly validates the text bounds behavior in various scenarios:

1. Without canvas
2. With canvas
3. After text update
4. After size update

packages/ui/src/component/advanced/Text.ts (1)

601-602: LGTM! Fix for text bounds when root canvas is missing.

The addition of the root canvas check in the visibility conditions correctly addresses the issue with text bounds when no root canvas is present.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.59%. Comparing base (214c693) to head (90c55fc).
Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2543      +/-   ##
==========================================
+ Coverage   68.53%   68.59%   +0.05%     
==========================================
  Files         961      961              
  Lines      100222   100219       -3     
  Branches     8572     8595      +23     
==========================================
+ Hits        68691    68743      +52     
+ Misses      31271    31216      -55     
  Partials      260      260              

Flag	Coverage Δ
unittests	68.59% <100.00%> (+0.05%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.