feat(macOS): Hide window control buttons when enable cover wall in zune and phone size

[XMLHexagram]

Summary by Sourcery

New Features:

• Hide window control buttons on macOS when the application is in Zune or Phone size and the cover wall is enabled.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR modifies the window control buttons visibility logic for macOS, specifically handling their visibility when the cover wall is enabled in Zune and Phone device types. The implementation updates the updateWindowControlButtons method to include additional conditions for hiding the window controls.

Class diagram for _WindowFrameForMacOSState changes

classDiagram
    class _WindowFrameForMacOSState {
        - FullScreenProvider _fullscreen
        - ResponsiveProvider _responsiveProvider
        + void didChangeDependencies()
        + void updateWindowControlButtons()
    }
    class MacOSWindowControlButtonManager {
        + static MacOSWindowControlButtonManager shared
        + void setHide()
        + void setShow()
        + void setVertical()
    }
    class ResponsiveProvider {
        + DeviceType currentDeviceType
    }
    class DeviceType {
        <<enumeration>>
        band
        dock
        zune
        phone
    }
    _WindowFrameForMacOSState --> MacOSWindowControlButtonManager
    _WindowFrameForMacOSState --> ResponsiveProvider
    ResponsiveProvider --> DeviceType

Loading

File-Level Changes

Change	Details	Files
Refactored window control buttons visibility logic	Extracted device type into a local variable for better readability Added new condition to hide controls when in cover wall view for Zune and Phone devices Restructured the method with early returns for better flow control Maintained existing behavior for band and dock device types	lib/widgets/title_bar/window_frame_for_macos.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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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 @XMLHexagram - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider injecting the router or passing the current path as a parameter instead of accessing $router globally, to improve testability and make dependencies explicit

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.}