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

Scenes/Dashboard: Adjust duplication logic to more closely match old architecture #87635

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

Conversation

kaydelaney
Copy link
Contributor

Ensures duplicated panel has same size as original panel.
Placement of duplicate panel is adjusted to be to the right of the original panel where possible.

@kaydelaney kaydelaney added area/dashboard area/frontend no-backport Skip backport of PR no-changelog Skip including change in changelog/release notes area/scenes labels May 10, 2024
@kaydelaney kaydelaney self-assigned this May 10, 2024
@kaydelaney kaydelaney requested a review from a team as a code owner May 10, 2024 14:06
@kaydelaney kaydelaney requested review from axelavargas, ivanortegaalba and dprokop and removed request for a team May 10, 2024 14:06
@grafana-delivery-bot grafana-delivery-bot bot added this to the 11.1.x milestone May 10, 2024
Copy link
Contributor

@ivanortegaalba ivanortegaalba left a comment

Choose a reason for hiding this comment

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

Tested it, and it works as expected.

However, I see the inconsistencies with adding a visualization to a dashboard. I'd try to reuse the logic of adding a panel into a dashboard for both places.

@Ijin08 when adding a panel, or duplicating it. Where would you expect to get the added visualization? Below or next to the current panel?

IMO, it seems more natural to add it next to it. If it doesn't fit, then it can go below.

Thoughts?

Copy link
Contributor

Choose a reason for hiding this comment

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

I'd add some test for this logic :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard area/frontend area/scenes no-backport Skip backport of PR no-changelog Skip including change in changelog/release notes
Projects
Status: 🔍 In review
Development

Successfully merging this pull request may close these issues.

None yet

2 participants