Files
superset2/docs/developer_docs_versioned_docs/version-6.1.0/api/schemas/chartdataextras.Schema.json
Claude Code cbcfd9599f docs: cut 6.1.0 versions for docs, admin_docs, developer_docs, components
Snapshots all four versioned Docusaurus sections at v6.1.0. Built on
top of the version-cutting tooling work in chore/docs-cut-6.1.0-versions
so the snapshot benefits from:

- Auto-gen refresh before snapshotting (database pages from engine
  spec metadata, API reference from openapi.json, component pages
  from Storybook stories) — captured at the SHA we cut from rather
  than whatever happened to be on disk.
- Data-import freeze: country list, feature flag table, database
  diagnostics, and component metadata are copied into snapshot-local
  `_versioned_data/` dirs so the historical version doesn't silently
  mutate when the source files change.
- Depth-aware import-path rewriter that handles deeply-nested
  component MDX files referencing `../../../src/` from the snapshot.

Versioning behavior: `lastVersion` stays at `current` for every
section, so the canonical URLs (`/docs/...`, `/admin-docs/...`,
`/developer-docs/...`, `/components/...`) continue to render content
from master. The `current` version is consistently labeled "Next"
with an `unreleased` banner, and `6.1.0` is a historical pin
accessible only via its explicit version segment.

Component playground: previously `disabled: true` in versions-config.json,
now enabled and versioned. The plugin block in docusaurus.config.ts
was already gated only by the `disabled` flag, so no other code
changes were needed to bring it back online.

The frozen `databases.json` in the snapshot is the canonical 80-database
artifact from the latest committed state in master (preserved by the
generator's input-hash cache), not a fallback regenerated from a
local Flask environment.
2026-05-13 17:15:46 -07:00

2 lines
1.7 KiB
JSON

{"schema":{"properties":{"column_order":{"description":"Ordered list of column names for result ordering. Used to preserve user's column reordering (including mixed dimension columns and metrics)","items":{"type":"string"},"nullable":true,"type":"array"},"having":{"description":"HAVING clause to be added to aggregate queries using AND operator.","type":"string"},"instant_time_comparison_range":{"description":"This is only set using the new time comparison controls that is made available in some plugins behind the experimental feature flag.","nullable":true,"type":"string"},"relative_end":{"description":"End time for relative time deltas. Default: `config[\"DEFAULT_RELATIVE_START_TIME\"]`","enum":["today","now"],"type":"string"},"relative_start":{"description":"Start time for relative time deltas. Default: `config[\"DEFAULT_RELATIVE_START_TIME\"]`","enum":["today","now"],"type":"string"},"time_grain_sqla":{"description":"To what level of granularity should the temporal column be aggregated. Supports [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601#Durations) durations.","enum":["PT1S","PT5S","PT30S","PT1M","PT5M","PT10M","PT15M","PT30M","PT1H","PT6H","P1D","P1W","P1M","P3M","P1Y","1969-12-28T00:00:00Z/P1W","1969-12-29T00:00:00Z/P1W","P1W/1970-01-03T00:00:00Z","P1W/1970-01-04T00:00:00Z",null],"example":"P1D","nullable":true,"type":"string"},"transpile_to_dialect":{"description":"If true, WHERE/HAVING clauses will be transpiled to the target database dialect using SQLGlot.","nullable":true,"type":"boolean"},"where":{"description":"WHERE clause to be added to queries using AND operator.","type":"string"}},"type":"object","title":"ChartDataExtras"},"schemaType":"response"}