fix: LineChartDataPoint.tooltip with escape characters not being properly rendered

[ndonkoHenri]

Description

Fixes #4049

Summary by Sourcery

Fix the rendering of LineChartDataPoint.tooltip with escape characters by decoding the tooltip string before displaying it.

Bug Fixes:

• Fix the issue where LineChartDataPoint.tooltip with escape characters was not being properly rendered by decoding the tooltip string.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request addresses an issue with the rendering of tooltips containing escape characters in the LineChartDataPoint class. The fix involves using jsonDecode to properly handle tooltip text that may contain escape characters.

No sequence diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Modify tooltip text processing in LineChartControl	Replace direct assignment of tooltip text with conditional logic Use jsonDecode to parse tooltip text if it exists Fallback to y-value string representation if tooltip is null	packages/flet/lib/src/controls/linechart.dart

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @ndonkoHenri - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider wrapping the jsonDecode call in a try-catch block, falling back to the original tooltip string if parsing fails. This would improve error handling and maintain backwards compatibility for non-JSON tooltip strings.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}