Skip to content

Docs: Add value mappings how-to guide for panel plugins#2607

Draft
leventebalogh wants to merge 1 commit intomainfrom
leventebalogh/docs-value-mappings
Draft

Docs: Add value mappings how-to guide for panel plugins#2607
leventebalogh wants to merge 1 commit intomainfrom
leventebalogh/docs-value-mappings

Conversation

@leventebalogh
Copy link
Copy Markdown
Collaborator

@leventebalogh leventebalogh commented Apr 30, 2026

Fixes: https://github.com/grafana/grafana-catalog-team/issues/280

What changed?

Added a new how-to guide under Panel plugins that explains how to enable and use value mappings in a panel plugin. Covers calling useFieldConfig(), reading mapped values via field.display(), and using getFieldDisplayValues for reduced values. Also added the new page to the sidebar.

Notes for the reviewer:
The guide intentionally doesn't duplicate the end-user value mappings docs — it links to them instead and focuses purely on the plugin developer perspective.

@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. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs.

@leventebalogh leventebalogh moved this from 📬 Triage to 🧑‍💻 In development in Grafana Catalog Team Apr 30, 2026
@leventebalogh leventebalogh self-assigned this Apr 30, 2026
@leventebalogh leventebalogh added no-changelog Don't include in changelog and version calculations type/docs Changes only affect the documentation labels Apr 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog Don't include in changelog and version calculations type/docs Changes only affect the documentation

Projects

Status: 🧑‍💻 In development

Development

Successfully merging this pull request may close these issues.

1 participant