You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c1eb5b6
Browse filesBrowse the repository at this point in the historyBrowse files
|**chart**|`{ chartType?: Enum<'bar' \| 'line' \| 'pie' \| 'area' \| 'scatter'>; dataset: string; dimensions?: string[]; values: string[] }`| optional |Chart binding — applies when the view renders as a chart. A `type: 'chart'`view must bind one: it names the ADR-0021 `dataset` and the measures (`values`) the chart plots, and there is no default binding|
789
789
|**map**|`{ latitudeField?: string; longitudeField?: string; locationField?: string; titleField?: string; … }`| optional | Map configuration — applies when the view renders as a map layout |
790
790
|**tree**|`{ parentField?: string; labelField?: string; fields?: string[]; defaultExpandedDepth?: integer }`| optional | Tree/hierarchy configuration — applies when the view renders as a tree layout |
791
791
|**pageName**|`never`| optional |[REMOVED]`view.pageName` was removed in @objectstack/spec 17.5.0 (ADR-0049 enforce-or-remove) — it named the page a `type: 'page'` view was to mount, and that mount was never built: no renderer read the key, so the named page was never reached and the view drew an empty grid. Delete the key; to put a published page in front of users, give the app a navigation item — `{ type: 'page', pageName: '<page_name>' }` under the app's `navigation` — which is a different key on a different surface and is the page mount that has always rendered. Run `os migrate meta --from 17` to list the mechanical edits for existing sources; `--write` applies the ones it can prove, and you apply the rest by hand. |
@@ -1177,7 +1177,7 @@ View filter rule
1177
1177
|**gantt**|`{ startDateField: string; endDateField: string; titleField: string; progressField?: string; … }`| optional | Gantt-timeline configuration — applies when the view renders as a gantt layout |
|**chart**|`{ chartType?: Enum<'bar' \| 'line' \| 'pie' \| 'area' \| 'scatter'>; dataset: string; dimensions?: string[]; values: string[] }`| optional |Chart binding — applies when the view renders as a chart. A `type: 'chart'`view must bind one: it names the ADR-0021 `dataset` and the measures (`values`) the chart plots, and there is no default binding|
1181
1181
|**map**|`{ latitudeField?: string; longitudeField?: string; locationField?: string; titleField?: string; … }`| optional | Map configuration — applies when the view renders as a map layout |
1182
1182
|**tree**|`{ parentField?: string; labelField?: string; fields?: string[]; defaultExpandedDepth?: integer }`| optional | Tree/hierarchy configuration — applies when the view renders as a tree layout |
1183
1183
|**pageName**|`never`| optional |[REMOVED]`view.pageName` was removed in @objectstack/spec 17.5.0 (ADR-0049 enforce-or-remove) — it named the page a `type: 'page'` view was to mount, and that mount was never built: no renderer read the key, so the named page was never reached and the view drew an empty grid. Delete the key; to put a published page in front of users, give the app a navigation item — `{ type: 'page', pageName: '<page_name>' }` under the app's `navigation` — which is a different key on a different surface and is the page mount that has always rendered. Run `os migrate meta --from 17` to list the mechanical edits for existing sources; `--write` applies the ones it can prove, and you apply the rest by hand. |
@@ -1760,7 +1760,7 @@ Tab configuration for multi-tab view interface
1760
1760
|**gantt**|`{ startDateField: string; endDateField: string; titleField: string; progressField?: string; … }`| optional | Gantt-timeline configuration — applies when the view renders as a gantt layout |
|**chart**|`{ chartType?: Enum<'bar' \| 'line' \| 'pie' \| 'area' \| 'scatter'>; dataset: string; dimensions?: string[]; values: string[] }`| optional |Chart binding — applies when the view renders as a chart. A `type: 'chart'`view must bind one: it names the ADR-0021 `dataset` and the measures (`values`) the chart plots, and there is no default binding|
1764
1764
|**map**|`{ latitudeField?: string; longitudeField?: string; locationField?: string; titleField?: string; … }`| optional | Map configuration — applies when the view renders as a map layout |
1765
1765
|**tree**|`{ parentField?: string; labelField?: string; fields?: string[]; defaultExpandedDepth?: integer }`| optional | Tree/hierarchy configuration — applies when the view renders as a tree layout |
1766
1766
|**pageName**|`never`| optional |[REMOVED]`view.pageName` was removed in @objectstack/spec 17.5.0 (ADR-0049 enforce-or-remove) — it named the page a `type: 'page'` view was to mount, and that mount was never built: no renderer read the key, so the named page was never reached and the view drew an empty grid. Delete the key; to put a published page in front of users, give the app a navigation item — `{ type: 'page', pageName: '<page_name>' }` under the app's `navigation` — which is a different key on a different surface and is the page mount that has always rendered. Run `os migrate meta --from 17` to list the mechanical edits for existing sources; `--write` applies the ones it can prove, and you apply the rest by hand. |
@@ -1845,7 +1845,7 @@ Tab configuration for multi-tab view interface
1845
1845
|**gantt**|`{ startDateField: string; endDateField: string; titleField: string; progressField?: string; … }`| optional | Gantt-timeline configuration — applies when the view renders as a gantt layout |
|**chart**|`{ chartType?: Enum<'bar' \| 'line' \| 'pie' \| 'area' \| 'scatter'>; dataset: string; dimensions?: string[]; values: string[] }`| optional |Chart binding — applies when the view renders as a chart. A `type: 'chart'`view must bind one: it names the ADR-0021 `dataset` and the measures (`values`) the chart plots, and there is no default binding|
1849
1849
|**map**|`{ latitudeField?: string; longitudeField?: string; locationField?: string; titleField?: string; … }`| optional | Map configuration — applies when the view renders as a map layout |
1850
1850
|**tree**|`{ parentField?: string; labelField?: string; fields?: string[]; defaultExpandedDepth?: integer }`| optional | Tree/hierarchy configuration — applies when the view renders as a tree layout |
1851
1851
|**pageName**|`never`| optional |[REMOVED]`view.pageName` was removed in @objectstack/spec 17.5.0 (ADR-0049 enforce-or-remove) — it named the page a `type: 'page'` view was to mount, and that mount was never built: no renderer read the key, so the named page was never reached and the view drew an empty grid. Delete the key; to put a published page in front of users, give the app a navigation item — `{ type: 'page', pageName: '<page_name>' }` under the app's `navigation` — which is a different key on a different surface and is the page mount that has always rendered. Run `os migrate meta --from 17` to list the mechanical edits for existing sources; `--write` applies the ones it can prove, and you apply the rest by hand. |
@@ -2086,7 +2086,7 @@ This schema accepts one of the following structures:
2086
2086
|**gantt**|`{ startDateField: string; endDateField: string; titleField: string; progressField?: string; … }`| optional | Gantt-timeline configuration — applies when the view renders as a gantt layout |
|**chart**|`{ chartType?: Enum<'bar' \| 'line' \| 'pie' \| 'area' \| 'scatter'>; dataset: string; dimensions?: string[]; values: string[] }`| optional |Chart binding — applies when the view renders as a chart. A `type: 'chart'`view must bind one: it names the ADR-0021 `dataset` and the measures (`values`) the chart plots, and there is no default binding|
2090
2090
|**map**|`{ latitudeField?: string; longitudeField?: string; locationField?: string; titleField?: string; … }`| optional | Map configuration — applies when the view renders as a map layout |
2091
2091
|**tree**|`{ parentField?: string; labelField?: string; fields?: string[]; defaultExpandedDepth?: integer }`| optional | Tree/hierarchy configuration — applies when the view renders as a tree layout |
2092
2092
|**pageName**|`never`| optional |[REMOVED]`view.pageName` was removed in @objectstack/spec 17.5.0 (ADR-0049 enforce-or-remove) — it named the page a `type: 'page'` view was to mount, and that mount was never built: no renderer read the key, so the named page was never reached and the view drew an empty grid. Delete the key; to put a published page in front of users, give the app a navigation item — `{ type: 'page', pageName: '<page_name>' }` under the app's `navigation` — which is a different key on a different surface and is the page mount that has always rendered. Run `os migrate meta --from 17` to list the mechanical edits for existing sources; `--write` applies the ones it can prove, and you apply the rest by hand. |
@@ -2264,7 +2264,7 @@ This schema accepts one of the following structures:
2264
2264
|**gantt**|`{ startDateField: string; endDateField: string; titleField: string; progressField?: string; … }`| optional | Gantt-timeline configuration — applies when the view renders as a gantt layout |
|**chart**|`{ chartType?: Enum<'bar' \| 'line' \| 'pie' \| 'area' \| 'scatter'>; dataset: string; dimensions?: string[]; values: string[] }`| optional |Chart binding — applies when the view renders as a chart. A `type: 'chart'`view must bind one: it names the ADR-0021 `dataset` and the measures (`values`) the chart plots, and there is no default binding|
2268
2268
|**map**|`{ latitudeField?: string; longitudeField?: string; locationField?: string; titleField?: string; … }`| optional | Map configuration — applies when the view renders as a map layout |
2269
2269
|**tree**|`{ parentField?: string; labelField?: string; fields?: string[]; defaultExpandedDepth?: integer }`| optional | Tree/hierarchy configuration — applies when the view renders as a tree layout |
2270
2270
|**pageName**|`never`| optional |[REMOVED]`view.pageName` was removed in @objectstack/spec 17.5.0 (ADR-0049 enforce-or-remove) — it named the page a `type: 'page'` view was to mount, and that mount was never built: no renderer read the key, so the named page was never reached and the view drew an empty grid. Delete the key; to put a published page in front of users, give the app a navigation item — `{ type: 'page', pageName: '<page_name>' }` under the app's `navigation` — which is a different key on a different surface and is the page mount that has always rendered. Run `os migrate meta --from 17` to list the mechanical edits for existing sources; `--write` applies the ones it can prove, and you apply the rest by hand. |
0 commit comments