fix: fix warnings.

[wjyrich]

as title.

Log:

Summary by Sourcery

Bug Fixes:

• Use strict equality (===) and strict inequality (!==) instead of == and != across width/height bindings, animation logic, visibility checks, cursor selection, and resizing calculations in main.qml.

[sourcery-ai]

Reviewer's Guide

This PR replaces all loose equality and inequality operators with strict equivalents in the dock panel’s QML code to address lint warnings without altering functional behavior.

Updated Class Diagram for QML Components in main.qml

classDiagram
    class Window {
        +real width
        +real height
    }
    class DockTransformPropertyAnimation {
        +variant to
        +void onStopped()
    }
    class HideSequentialAnimation {
        +void onStopped()
    }
    class DragMouseArea {
        +var cursorShape
        +void onPositionChanged()
    }
    Window "1" *-- "1..*" DockTransformPropertyAnimation : contains
    Window "1" *-- "1" HideSequentialAnimation : contains
    Window "1" *-- "1" DragMouseArea : contains

Loading

File-Level Changes

Change	Details	Files
Enforce strict equality operators across QML code	Use ===/!== in width and height property bindings Use ===/!== in animation ‘to’ expressions and hide/show state checks Use ===/!== in visibility toggles after animation stops Use ===/!== in cursor type determination based on panel position Use ===/!== in dock resizing logic for drag events	panels/dock/package/main.qml

---

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. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

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 @wjyrich - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 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.}

[deepin-ci-robot]

deepin pr auto review

代码审查意见：

1. 代码风格一致性：

   • 在修改后的代码中，使用了严格相等运算符 === 替换了非严格相等运算符 ==，这是一个好的做法，因为它可以避免类型转换带来的潜在问题。建议在整个项目中保持这一风格，以提高代码的一致性和可读性。

2. 逻辑判断：

   • 代码中多次使用了 Panel.position === Dock.Top 或 Panel.position === Dock.Bottom 的判断，这表明 Panel.position 和 Dock.Top、Dock.Bottom 的比较是频繁的。如果 Dock 枚举值较多，建议使用一个映射或查找表来简化这些判断，以提高代码的可维护性。

3. 性能考虑：

   • 在计算 newDockSize 时，使用了 Math.min 和 Math.max 函数，这些函数在性能上通常没有问题，但如果 Dock.MIN_DOCK_SIZE 和 Dock.MAX_DOCK_SIZE 的值变化频繁，可以考虑缓存这些值，以减少重复计算。

4. 安全性：

   • 代码中没有明显的安全问题，但建议确保所有用户输入都经过适当的验证和清理，以防止潜在的注入攻击。

5. 代码注释：

   • 虽然代码中添加了一些注释，但建议增加更多的注释来解释复杂的逻辑和关键步骤，特别是对于新加入项目的开发者来说，这些注释将非常有帮助。

6. 代码重构：

   • 代码中的一些重复逻辑，如 Panel.position === Dock.Top 或 Panel.position === Dock.Bottom 的判断，可以考虑提取成一个函数或常量，以减少代码重复和提高代码的可读性。

综上所述，代码的修改是合理的，但建议在保持代码风格一致性的同时，考虑上述几点来进一步优化代码质量和性能。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BLumia, wjyrich

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment