Skip to content

Chore: Update slider selector#2604

Merged
ashharrison90 merged 7 commits intomainfrom
ash/update-slider-selector
May 6, 2026
Merged

Chore: Update slider selector#2604
ashharrison90 merged 7 commits intomainfrom
ash/update-slider-selector

Conversation

@ashharrison90
Copy link
Copy Markdown
Contributor

@ashharrison90 ashharrison90 commented Apr 30, 2026

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

📦 Published PR as canary version: Canary Versions

✨ Test out this PR locally via:

npm install website@5.5.4-canary.2604.25389071972.0
npm install @grafana/create-plugin@7.3.1-canary.2604.25389071972.0
npm install @grafana/plugin-e2e@3.7.1-canary.2604.25389071972.0
# or 
yarn add website@5.5.4-canary.2604.25389071972.0
yarn add @grafana/create-plugin@7.3.1-canary.2604.25389071972.0
yarn add @grafana/plugin-e2e@3.7.1-canary.2604.25389071972.0

@ashharrison90 ashharrison90 requested a review from a team April 30, 2026 08:50
@ashharrison90 ashharrison90 self-assigned this Apr 30, 2026
@ashharrison90 ashharrison90 requested review from Copilot and removed request for a team April 30, 2026 08:50
@ashharrison90 ashharrison90 requested a review from a team as a code owner April 30, 2026 08:50
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 30, 2026

Hello! 👋 This repository uses Auto for releasing packages using PR labels.

✨ This PR can be merged and will trigger a new patch release.
NOTE: When merging a PR with the release label please avoid merging another PR. For further information see here.

@ashharrison90 ashharrison90 added patch Increment the patch version when merged release Create a release when this pr is merged labels Apr 30, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the PanelEditOptionsGroup slider input locator logic to match Grafana UI changes across versions, ensuring plugin-e2e can continue to find and interact with slider-backed option inputs.

Changes:

  • Treat Grafana >= 13.0.0 slider inputs as text inputs.
  • Keep Grafana >= 9.1.0 and < 13.0.0 slider inputs mapped to number inputs (spinbuttons).
  • Use the shared getTextInput() helper for the fallback path.

Comment on lines 60 to 63
if (gte(this.ctx.grafanaVersion, '13.0.0')) {
return this.getTextInput(label);
}
if (gte(this.ctx.grafanaVersion, '9.1.0')) {
Copy link

Copilot AI Apr 30, 2026

Choose a reason for hiding this comment

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

The >=13.0.0 branch currently returns the same locator as the default fallback (text input). Consider simplifying this to a single version range check (e.g., only special-case the versions where the slider is a spinbutton) and/or add a brief note about the Grafana UI change that requires treating v13 differently to avoid confusion later.

Suggested change
if (gte(this.ctx.grafanaVersion, '13.0.0')) {
return this.getTextInput(label);
}
if (gte(this.ctx.grafanaVersion, '9.1.0')) {
if (gte(this.ctx.grafanaVersion, '9.1.0') && !gte(this.ctx.grafanaVersion, '13.0.0')) {

Copilot uses AI. Check for mistakes.
return this.getNumberInput(label);
}
return this.getFieldLocator(label).getByRole('textbox');
return this.getTextInput(label);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this seems scary to change 🤔

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@hugohaggmark this.getTextInput(label) is exactly the same as this.getFieldLocator(label).getByRole('textbox'), i was just trying to simplify a bit 😅 i don't care about this bit at all so i can remove if needed

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

ok, thanks for explaination

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

there are tests broken, I'll wait a bit with approval until you looked at those

Copy link
Copy Markdown
Contributor Author

@ashharrison90 ashharrison90 Apr 30, 2026

Choose a reason for hiding this comment

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

@hugohaggmark i don't believe these are related to this PR sadly 😭

it also doesn't seem to be pushing canaries either

@grafana-plugins-platform-bot grafana-plugins-platform-bot Bot moved this from 📬 Triage to 🔬 In review in Grafana Catalog Team Apr 30, 2026
hugohaggmark
hugohaggmark previously approved these changes May 5, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

Playwright test results

Image Name Version Result Report
grafana-enterprise nightly
grafana-enterprise dev-preview-react19
grafana-enterprise 13.0.1
grafana-enterprise 12.1.10
grafana-enterprise 11.0.11
grafana-enterprise 9.3.16
grafana-enterprise 8.5.27
Troubleshooting

404 when clicking on View report

By default, the deploy-report-pages Action deploys reports to the gh-pages branch. However, you need to take an extra step to ensure that GitHub Pages can build and serve the site from this branch. To do so:

  1. Go to the Settings tab of your repository.
  2. In the left-hand sidebar, click on Pages.
  3. Under Source, select Deploy from a branch, then choose the gh-pages branch.

This action needs to be completed manually in order for your GitHub Pages site to be built and accessible from the gh-pages branch. Once configured, GitHub will automatically build and serve the site whenever new reports are deployed.

Copy link
Copy Markdown
Contributor

@sunker sunker left a comment

Choose a reason for hiding this comment

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

🚀

@ashharrison90 ashharrison90 merged commit 25da1d8 into main May 6, 2026
68 of 75 checks passed
@ashharrison90 ashharrison90 deleted the ash/update-slider-selector branch May 6, 2026 09:14
@github-project-automation github-project-automation Bot moved this from 🔬 In review to 🚀 Shipped in Grafana Catalog Team May 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

patch Increment the patch version when merged release Create a release when this pr is merged

Projects

Status: 🚀 Shipped

Development

Successfully merging this pull request may close these issues.

4 participants