grafana/docs
Kyle Cunningham 80e7f54166
Table Panel: Refactor Cell Options to Allow for Options per Cell Type (#59363)
* Update table data structure schema.

* Update table panel configuration options for new structure

* Fix TS errors from refactor

* Separate background and gauge display modes

* Remove the now used Bar Gauge display from the mud

* Fix types up

* Reorganize data structures

* Fix type issues.

* Start stubbing necessary code.

* Continue implementing option refactor

* Change category for cell type selection.

* Consolidate cell options

* Fix various typing issues

* Clean up dead code

* Stub handling display mode changes

* Make subOption editor dynamic

* Setup interface for sub-option editor props

* Remove unused imports

* Remove console.log call

* Persist display mode changes, stub sub options change, update comments.

* Make sure updates from cells are persisted

* Persist sub-option changes

* Update BarGaugeCell to take into account new settings.

* Add deprecated field back

* Remove unecessary options in configuration

* Update default cell to accept new settings

* Make sure color text display works

* Add deprecated property notice

* Use constant as opposed to string

* Make sure we name globally namespaced things uniquely

* Update to use unique name

* Use union type with discriminator.

* Simplify types and operation

* Update type definitons

* Update types

* Update property names in cells

* Remove React.FC usage

* Update option editor signature

* Update options structure

* Change variable name

* Fix "Color Text" display

* Remove debug statement

* Make sure we remain backwards compatible with display mode.

* Add migration for configuration.

* Export BarGaugeDisplayMode from grafana-ui

* Update import

* Fix bar gauge and dashboard migrator tests

* Fix potential undefined references causing test failures

* Fix another potential reference error in DefaultCell

* Try to fix breaking change detection.

* Cache setting changes

* Make sure we return with onChange invocation

* Fixed migrating overrides

* Fix a number of review comments

* Simplify option editors

* Fix unused imports

* Fill out comments for types

* Actually use defaultPanelConfig for editor default

* Move TableCellEditorProps alongside TableCellOptionEditor

* Update docs for table panel

* Also make sure we remove TableCellEditorProps from model file

* Stub migration tests

* Add tests for default config migration

* Add basic overrides test

* Flesh out tests a bit more

* Add inspect to same category as cell editor

Co-authored-by: Torkel Ödegaard <torkel@grafana.com>
2023-01-12 18:42:57 +07:00
..
sources Table Panel: Refactor Cell Options to Allow for Options per Cell Type (#59363) 2023-01-12 18:42:57 +07:00
.gitignore Docs: Add minimal hugo build, update docs README (#20905) 2019-12-13 15:47:28 +01:00
logo-horizontal.png Added back logo file (#21198) 2019-12-19 09:09:48 -08:00
Makefile Docs: Deprecating packages_api and removing it from our pipelines (#54473) 2022-09-01 18:15:44 +02:00
README.md Update README.md (#43358) 2022-02-17 14:27:15 +00:00

Building the docs locally

When you contribute to documentation, it is a good practice to build the docs on your local machine to make sure your changes appear as you expect. This README explains the process for doing that.

Requirements

Docker >= 2.1.0.3 Yarn >= 1.22.4

Build the doc site

  1. On the command line, first change to the docs folder: cd docs.
  2. Run make docs. This launches a preview of the website with the current grafana docs at http://localhost:3002/docs/grafana/next/ which will refresh automatically when changes are made to content in the sources directory.

If you have the grafana/website repo checked out in the same directory as the grafana repo, then you can run make docs-local-static to use local assets (such as images).


Content guidelines

Edit content in the sources directory.

Contributing

Use the Hugo shortcode relref any time you are linking to other internal docs pages.

Syntax is:

{{< relref "example.md" >}}

You might need to add more context for the link (containing folders and so on, folder/example.md) if Hugo says the relref is ambiguous.

Managing redirects

When moving content around or removing pages it's important that users following old links are properly redirected to the new location. We do this using the aliases feature in Hugo.

If you are moving a page, add an aliases entry in the front matter referencing the old location of the page which will redirect the old url to the new location.

If you are removing a page, add an aliases entry in the front matter of the most-applicable page referencing the location of the page being removed.

If you are copying an existing page as the basis for a new one, be sure to remove any aliases entries in the front matter in your copy to avoid conflicting redirects.

Edit the side menu

The side menu is automatically build from the file structure. Use the weight front matter parameter to order pages.

To specify different menu text from the page title, use the front matter parameter menuTitle.

Add images

Images are currently hosted in the grafana/website repo.


Deploy changes to grafana.com

When a PR is merged with changes in the docs/sources directory, those changes are automatically synced by a GitHub action (.github/workflows/publish.yml) to the grafana/website repo.

  • A PR that targets the main branch syncs to the content/docs/grafana/next directory in the website repository, and publishes to https://grafana.com/docs/grafana/next/.
  • A PR targeting the latest/current release branch syncs to the content/docs/grafana/latest directory in the website repository, and publishes to https://grafana.com/docs/grafana/latest/.

Once the sync is complete, the website will automatically publish to production - no further action is needed.