Files
superset2/docs/developer_docs_versioned_docs/version-6.1.0/api/schemas/chartdatarollingoptionsschema.Schema.json
Claude Code 4ee42fe5b8 docs: cut 6.1.0 versions for user_docs, admin_docs, developer_docs, components
Snapshots all four versioned Docusaurus sections at v6.1.0, cut from
master after the version-cutting tooling (#39837), broken-internal-
links fix (#40102), and user_docs rename (#40171) all landed. With
the rename in place, all four sections now produce parallel-named
files at the docs/ root (no more bare `versioned_docs/` outlier).

Versioning behavior: lastVersion stays at current for every section,
so the canonical URLs (/user-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.

Snapshot includes:
- All MDX content for the four sections.
- Auto-gen captured fresh: 74 database pages (engine spec metadata),
  ~1,800 API reference files (openapi.json), 59 component pages
  (Storybook stories).
- Data imports frozen at cut time into snapshot-local _versioned_data/
  dirs:
    user_docs_versioned_docs/version-6.1.0/_versioned_data/src/data/databases.json
      (canonical 80-database diagnostics from master, preserved by the
      generator's input-hash cache)
    admin_docs_versioned_docs/version-6.1.0/_versioned_data/data/countries.json
    admin_docs_versioned_docs/version-6.1.0/_versioned_data/static/feature-flags.json
    developer_docs_versioned_docs/version-6.1.0/_versioned_data/static/data/components.json
- Import paths in deeply-nested files rewritten so they still resolve
  from one directory deeper inside the snapshot.
- developer_docs/extensions/overview.md snapshot has the FIXED
  ./mcp.md form (from #40102), so the SPA-nav 404 isn't baked into
  the 6.1.0 version.

Verified via full yarn build: exit 0, no broken links surfaced by
onBrokenLinks: throw.
2026-05-15 22:36:30 -07:00

2 lines
1.5 KiB
JSON

{"schema":{"properties":{"center":{"description":"Should the label be at the center of the window.Default: `false`","example":false,"type":"boolean"},"min_periods":{"description":"The minimum amount of periods required for a row to be included in the result set.","example":7,"type":"integer"},"rolling_type":{"description":"Type of rolling window. Any numpy function will work.","enum":["average","argmin","argmax","cumsum","cumprod","max","mean","median","nansum","nanmin","nanmax","nanmean","nanmedian","nanpercentile","min","percentile","prod","product","std","sum","var"],"example":"percentile","type":"string"},"rolling_type_options":{"description":"Optional options to pass to rolling method. Needed for e.g. quantile operation.","example":{},"type":"object"},"win_type":{"description":"Type of window function. See [SciPy window functions](https://docs.scipy.org/doc/scipy/reference /signal.windows.html#module-scipy.signal.windows) for more details. Some window functions require passing additional parameters to `rolling_type_options`. For instance, to use `gaussian`, the parameter `std` needs to be provided.","enum":["boxcar","triang","blackman","hamming","bartlett","parzen","bohman","blackmanharris","nuttall","barthann","kaiser","gaussian","general_gaussian","slepian","exponential"],"type":"string"},"window":{"description":"Size of the rolling window in days.","example":7,"type":"integer"}},"required":["rolling_type","window"],"type":"object","title":"ChartDataRollingOptionsSchema"},"schemaType":"response"}