Skip to content
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

feat: add option to hide other Klipper & Moonraker instances #2029

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

meteyou
Copy link
Member

@meteyou meteyou commented Oct 15, 2024

Description

This PR adds an option to hide all other Klipper & Moonraker instances in the top right corner menu. This will be useful for multi instances. This PR will also hide the stop service button from the current Moonraker instance and fix the confirm dialog for other Klipper instances.

Related Tickets & Documents

fixes #2027

Mobile & Desktop Screenshots/Recordings

before:
image

after:
image

[optional] Are there any post-deployment tasks we need to perform?

none

Summary by Sourcery

Introduce a feature to hide other Klipper and Moonraker instances in the top corner menu, enhancing multi-instance management. Refactor the service management in the menu to use a new component, and fix the confirmation dialog for Klipper instances.

New Features:

  • Add an option to hide other Klipper and Moonraker instances in the top corner menu for better management of multiple instances.

Bug Fixes:

  • Fix the confirmation dialog for other Klipper instances.

Enhancements:

  • Refactor the top corner menu to use a new component for service management, improving code modularity and readability.

@meteyou meteyou requested review from dw-0 and rackrick October 15, 2024 22:23
@dosubot dosubot bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Oct 15, 2024
Copy link
Contributor

Language file analysis report:

File Missing Keys Unused Keys
en.json 0 0

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Overall Comments:

  • Great work on modularizing the code and adding the new feature. Consider profiling the changes to ensure there's no significant performance impact, especially with the added conditional logic.
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 ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@@ -0,0 +1,154 @@
<template>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: Add component description and usage comments

This new component improves modularity, but it would be helpful to add comments at the top of the file explaining its purpose and how it interacts with the parent component. This will make it easier for other developers to understand and use this component correctly.

<!-- TopCornerMenuService.vue -->
<!-- This component provides a configurable top corner menu dialog. -->
<!-- It is used to display alerts or confirmations in a modal format. -->
<!-- Props: show (Boolean), title (String), isMobile (Boolean) -->
<template>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:L This PR changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

power menu will get too long with many multi instances
1 participant