@adminforth/dashboard 1.11.1 → 1.11.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -476,6 +476,10 @@ query:
|
|
|
476
476
|
|
|
477
477
|
Do not use bare query.steps without source: steps.
|
|
478
478
|
Do not use metric. Use select even when a step has only one aggregate.
|
|
479
|
+
All filters, including aggregate select item filters, must use filter expression shape.
|
|
480
|
+
Use `filters: { field: model, eq: gpt-5.4 }`, not shorthand maps like `filters: { model: gpt-5.4 }`.
|
|
481
|
+
When grouping by a derived date alias, repeat the source field object in `group_by`.
|
|
482
|
+
Example: if `select` has `{ field: used_at, grain: day, as: day }`, use `group_by: [{ field: used_at, grain: day, as: day }]`, not `group_by: [day]`.
|
|
479
483
|
|
|
480
484
|
## Date range rules
|
|
481
485
|
|
|
@@ -476,6 +476,10 @@ query:
|
|
|
476
476
|
|
|
477
477
|
Do not use bare query.steps without source: steps.
|
|
478
478
|
Do not use metric. Use select even when a step has only one aggregate.
|
|
479
|
+
All filters, including aggregate select item filters, must use filter expression shape.
|
|
480
|
+
Use `filters: { field: model, eq: gpt-5.4 }`, not shorthand maps like `filters: { model: gpt-5.4 }`.
|
|
481
|
+
When grouping by a derived date alias, repeat the source field object in `group_by`.
|
|
482
|
+
Example: if `select` has `{ field: used_at, grain: day, as: day }`, use `group_by: [{ field: used_at, grain: day, as: day }]`, not `group_by: [day]`.
|
|
479
483
|
|
|
480
484
|
## Date range rules
|
|
481
485
|
|