Skip to content

Docs: Add field overrides how-to guide for panel plugins#2606

Draft
leventebalogh wants to merge 1 commit intomainfrom
leventebalogh/field-overrides-docs
Draft

Docs: Add field overrides how-to guide for panel plugins#2606
leventebalogh wants to merge 1 commit intomainfrom
leventebalogh/field-overrides-docs

Conversation

@leventebalogh
Copy link
Copy Markdown
Collaborator

@leventebalogh leventebalogh commented Apr 30, 2026

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

What changed?

Adds a new how-to guide under Panel plugins that explains how to implement field override support in a panel plugin. It covers:

  • How field overrides work from a dashboard user's perspective (defaults vs. overrides, matchers)
  • Enabling standard field config with useFieldConfig()
  • Customizing standard options (defaults, disabling, settings)
  • Defining custom field config properties with the FieldConfigEditorBuilder
  • Controlling property visibility (category, showIf, shouldApply, hideFromDefaults/hideFromOverrides)
  • Accessing resolved field config in the panel component
  • A complete end-to-end example

Why?

There was no guidance on the developer portal about how to add field overrides to a panel plugin. This was a gap flagged in the catalog team issue above.

Add a new how-to guide for implementing field override support in panel
plugins, covering enabling standard field config, customizing standard
options, defining custom field config properties, and accessing resolved
config in the panel component.
@leventebalogh leventebalogh self-assigned this Apr 30, 2026
@leventebalogh leventebalogh moved this from 📬 Triage to 🧑‍💻 In development in Grafana Catalog Team Apr 30, 2026
@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 added type/docs Changes only affect the documentation no-changelog Don't include in changelog and version calculations 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