Skip to content

The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:

Update generated docs (master) (#66353)

github-automation-metabase0c4c8c06abaf
diff --git a/docs/api.json b/docs/api.json
index 76ac37be7f2..5cd5c8acc7c 100644
--- a/docs/api.json
+++ b/docs/api.json
@@ -1514,6 +1514,9 @@
"metabase-enterprise.metabot-v3.tools.api.column" : {
"type" : "object",
"properties" : {
+ "database_type" : {
+ "type" : "string"
+ },
"description" : {
"type" : "string"
},
@@ -2692,7 +2695,7 @@
"properties" : {
"field_granularity" : {
"type" : "string",
- "enum" : [ "day", "week", "month", "quarter", "year" ]
+ "enum" : [ "minute", "hour", "day", "week", "month", "quarter", "year", "day-of-week" ]
},
"field_id" : {
"type" : "string"
@@ -3163,6 +3166,9 @@
"$ref" : "#/components/schemas/metabase-enterprise.metabot-v3.tools.api.table-result"
}
},
+ "related_by" : {
+ "type" : "string"
+ },
"display_name" : {
"type" : "string"
},
@@ -4522,6 +4528,14 @@
"$ref" : "#/components/schemas/metabase.legacy-mbql.schema.UnnamedAggregation"
} ]
},
+ "metabase.legacy-mbql.schema.AggregationArg" : {
+ "description" : "Schema for the argument to an aggregation clause like `:sum`.\n\n Strings are allowed as literals here, unlike at the top level as `::Expressions`, so `::FieldOrExpressionDef` is\n not enough. However, nested aggregations are not allowed here, so we can't use `::ExpressionArg` either. (#66199)",
+ "anyOf" : [ {
+ "$ref" : "#/components/schemas/metabase.legacy-mbql.schema.FieldOrExpressionDef"
+ }, {
+ "type" : "string"
+ } ]
+ },
"metabase.legacy-mbql.schema.AggregationOptionsOptions" : {
"description" : "Additional options for any aggregation clause when wrapping it in `:aggregation-options`.",
"type" : "object",