Skip to content

Fix gauge chart API example units and note API versioning - #7593

Open
florent-leborgne wants to merge 1 commit into
mainfrom
docs-issue-7057-api-payload-fixes
Open

Fix gauge chart API example units and note API versioning#7593
florent-leborgne wants to merge 1 commit into
mainfrom
docs-issue-7057-api-payload-fixes

Conversation

@florent-leborgne

@florent-leborgne florent-leborgne commented Jul 27, 2026

Copy link
Copy Markdown
Member

Summary

Follow-up to the Dashboards and Visualizations API GA work (#7057).

  • gauge-charts.md: the duration format units in the API example used the old preview codes (microseconds/asMilliseconds). Updated to the GA schema unit codes (us/ms) so the request validates.
  • Added a shared note (_snippets/api-payload-version-note.md) before every API payload example, pointing readers to the Kibana and Elastic Cloud Serverless breaking changes release notes so they can track field changes across versions.

The area chart example keeps its inline data_view_spec for the query annotation. On 9.5 that currently returns a 500 (elastic/kibana#280977), but this is likely a bug that will be resolved, so the example reflects the intended behavior.

- gauge-charts.md: use the current duration format unit codes (us/ms) so
  the example validates against the GA Visualizations API schema.
- Add a shared note before every API payload example pointing readers to
  the Kibana and Serverless breaking changes release notes.

Co-authored-by: Cursor <cursoragent@cursor.com>
@florent-leborgne
florent-leborgne requested a review from a team as a code owner July 27, 2026 16:24
@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@vishaangelova vishaangelova left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants