@gooddata/sdk-maql-language-server 0.0.0-stage → 11.65.0-alpha.3

package/esm/docs/en/docs/create-metrics/maql/filters/overriding-parent/with-parent-except.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"with-parent-except.d.ts","sourceRoot":"","sources":["../../../../../../../../src/docs/en/docs/create-metrics/maql/filters/overriding-parent/with-parent-except.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,k0CAmCb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/filters/overriding-parent/with-parent-except.js

@@ -0,0 +1,37 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `Includes all parent filters, except for any filters specified as a
+comma-separated list of attributes.
+
+This clause can be shortened to WITH PF EXCEPT.
+
+In EXCEPT clauses, multiple attributes can be specified as a series of
+comma-separated values.
+
+## Example
+
+In the table below, you can see how the WITH PARENT
+FILTER EXCEPT keyword affects the filtered version of the visualization.
+
+
+| Definition               | Visualization Filter            | Metric Value |
+|--------------------------|--------------------------|--------------|
+| \`SELECT M1\`              | (none)                   | 500          |
+| \`SELECT M1\`              | F1: Group = X          | 350          |
+| \`SELECT M1\`              | F1: Group = X; F2: Priority is Y           | 250          |
+| \`SELECT M1 WITH PARENT FILTER EXCEPT {attribute/priority}\`  | F1: Group = X; F2: Priority is Y      | 350          |
+
+In the above example in the fourth row, the
+WITH PARENT FILTER EXCEPT includes all parent filters in the metric,
+except for one: Priority. So, in this case, the Priority filter is not
+applied to the metric. The generated metric value equates to the value
+generated in the version in the second row.
+
+## Syntax
+
+\`\`\`
+SELECT ... WITH PARENT FILTER EXCEPT Attribute1,...
+\`\`\`
+
+\`\`\`
+SELECT ... WITH PF EXCEPT Attribute1,...
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/filters/overriding-parent/with-parent-filter.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "Applies all parent filters to the metric. All parent filters specified\nin visualizations, dashboards, and any metrics in which this metric is nested\nare applied to the calculation.\n\nThis clause can be shortened to WITH PF.\n\nThe WITH PARENT keyword is applied by default when other visualization filters\nare not present.\n\n## Example\n\nIn the table below, you can see how the WITH PARENT FILTER clause\naffects the filtered version of the visualization.\n\n\n| Definition                        | Visualization Filter   | Metric Value |\n|-----------------------------------|-----------------|--------------|\n| `SELECT M1`                       | (none)          | 500          |\n| `SELECT M1`                       | F1: Group = X | 350          |\n| `SELECT (SELECT M1 WITH PARENT FILTER) WHERE Group = Y`            | F1: Group = X | null         |\n\nIn the third row above, the definition includes a nested metric in which\nparent filters are forced to be included from inside the nested metric.\n\n-   In the parent metric is the filter Group = Y.\n-   At the visualization level, the filter is Group = X.\n-   The WITH PARENT FILTER keyword means that all parent filters are\n    applied to the metric. During evaluation, both Group = X and Group =\n    Y are applied to the data as a logical AND. Since a data element may\n    be associated with a single attribute value, there are no data\n    elements that match both filters, and the result set is null.\n\n## Syntax\n\n```\nSELECT ... WITH PARENT FILTER\n```\n\n```\nSELECT ... WITH PF\n```";
+//# sourceMappingURL=with-parent-filter.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/filters/overriding-parent/with-parent-filter.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"with-parent-filter.d.ts","sourceRoot":"","sources":["../../../../../../../../src/docs/en/docs/create-metrics/maql/filters/overriding-parent/with-parent-filter.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,+hDAwCb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/filters/overriding-parent/with-parent-filter.js

@@ -0,0 +1,42 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `Applies all parent filters to the metric. All parent filters specified
+in visualizations, dashboards, and any metrics in which this metric is nested
+are applied to the calculation.
+
+This clause can be shortened to WITH PF.
+
+The WITH PARENT keyword is applied by default when other visualization filters
+are not present.
+
+## Example
+
+In the table below, you can see how the WITH PARENT FILTER clause
+affects the filtered version of the visualization.
+
+
+| Definition                        | Visualization Filter   | Metric Value |
+|-----------------------------------|-----------------|--------------|
+| \`SELECT M1\`                       | (none)          | 500          |
+| \`SELECT M1\`                       | F1: Group = X | 350          |
+| \`SELECT (SELECT M1 WITH PARENT FILTER) WHERE Group = Y\`            | F1: Group = X | null         |
+
+In the third row above, the definition includes a nested metric in which
+parent filters are forced to be included from inside the nested metric.
+
+-   In the parent metric is the filter Group = Y.
+-   At the visualization level, the filter is Group = X.
+-   The WITH PARENT FILTER keyword means that all parent filters are
+    applied to the metric. During evaluation, both Group = X and Group =
+    Y are applied to the data as a logical AND. Since a data element may
+    be associated with a single attribute value, there are no data
+    elements that match both filters, and the result set is null.
+
+## Syntax
+
+\`\`\`
+SELECT ... WITH PARENT FILTER
+\`\`\`
+
+\`\`\`
+SELECT ... WITH PF
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/filters/overriding-parent/without-parent-except.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "Remove parent filters, except for any filters specified as a comma-separated list of attributes.\n\nThis clause can be shortened to WITHOUT PF EXCEPT.\n\nIn EXCEPT clauses, multiple attributes may be specified as a series of\ncomma-separated values.\n\nExcepted attribute filters are applied to the specified attribute and to\nall attributes of coarser granularity in the hierarchy. For example, in\nthe hierarchy State-County-City, the values of the attribute City do not\ngroup the values of County, but County groups City because County has coarser granularity than City. So, if City is excepted, County and State\nare excepted too. If you apply the exception to the State attribute, it\nis the only attribute filter that is excepted.\n\n## Syntax\n\n```\nSELECT ... WITHOUT PARENT FILTER EXCEPT Attribute1,...\n```\n\n```\nSELECT ... WITHOUT PF EXCEPT Attribute1,...\n```\n\n## Example 1\n\nIn the table below, you can see how the WITHOUT PARENT FILTER EXCEPT\nkeyword works with the State-County-City hierarchy.\n\n\n| Definition                          | visualization Filter    | Metric Value |\n|-------------------------------------|------------------|--------------|\n| `SELECT M1`                         | (none)           | 1000         |\n| `SELECT M1`                         |  F1: County = X | 600          |\n| `SELECT M1 WITHOUT PF`              |  F1: County = X | 1000         |\n| `SELECT M1 WITHOUT PF EXCEPT City`  |  F1: County = X | 600          |\n| `SELECT M1 WITHOUT PF EXCEPT State` |  F1: County = X | 1000         |\n| `SELECT M1 WITHOUT PF EXCEPT State` |  F1: State = Y  | 550          |\n\n\n-   In the above example in the third row, the WITHOUT PARENT FILTER\n    removes all parent filters from the metric, so COUNTY = X is not\n    applied. The returned results match the unfiltered version of the\n    metric in the first row.\n-   In the fourth row, City is excepted. Since County has a coarser grain than City, the parent visualization filter (County = X) is applied.\n-   In the fifth row, the excepted filter is State. However, the visualization\n    filter is at the County attribute level, which is finer than State.\n    Therefore, the filter is not applied, and the results match the\n    unfiltered version in the first row.\n-   In the fifth row, the excepted filter is State, which matches the\n    visualization filter. So, the results are filtered.\n\n## Example 2\n\nIn the table below, you can see how the WITHOUT PARENT\nFILTER EXCEPT keyword affects the filtered version of the visualization.\n\n\n| Definition               | Visualization Filter            | Metric Value |\n|--------------------------|--------------------------|--------------|\n| `SELECT M1`              | (none)                   | 500          |\n| `SELECT M1`              |  F1: Group = X          | 350          |\n| `SELECT M1`              |  F1: Group =            | 250          |\n|                          | X; F2: Priority is Y    |              |\n| `SELECT M1 WITHOUT PARENT FILTER EXCEPT Group`   |  F1: Group = X; F2: Priority is Y           | 350          |\n\n\nIn the above example in the fourth row, the\nWITHOUT PARENT FILTER EXCEPT removes all parent filters from the metric,\nexcept for one: Group, so the Priority filter is not applied to the\nmetric. The generated metric value equates to the value generated in the\nversion in the second row.\n\n\n## Example 3\n\n  |Definition                                                                |  visualization Filter|\n  |---------------------------------------------------------------------------|---------------|\n  |`SELECT (SELECT M1 WITHOUT PF EXCEPT Date) WHERE (SELECT M2 BY Date) > Y`  | Group = X |\n\n\n-   M2 is filtered by group.\n-   M1 is not filtered by group, only by the numeric range filter in the\n    `WHERE` part.\n\n## Example 4\n\n| Definition                                          | Visualization Filter |\n|-----------------------------------------------------|---------------|\n| `SELECT (SELECT M1 WITHOUT PF EXCEPT Date) WHERE (SELECT M2 BY Date) > Y`    | Group = X  Date = Z   |\n\n-   M2 is filtered by group, date.\n-   M1 is filtered by date and the numeric range in the `WHERE` part.";
+//# sourceMappingURL=without-parent-except.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/filters/overriding-parent/without-parent-except.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"without-parent-except.d.ts","sourceRoot":"","sources":["../../../../../../../../src/docs/en/docs/create-metrics/maql/filters/overriding-parent/without-parent-except.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,soIA4FoD,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/filters/overriding-parent/without-parent-except.js

@@ -0,0 +1,94 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `Remove parent filters, except for any filters specified as a comma-separated list of attributes.
+
+This clause can be shortened to WITHOUT PF EXCEPT.
+
+In EXCEPT clauses, multiple attributes may be specified as a series of
+comma-separated values.
+
+Excepted attribute filters are applied to the specified attribute and to
+all attributes of coarser granularity in the hierarchy. For example, in
+the hierarchy State-County-City, the values of the attribute City do not
+group the values of County, but County groups City because County has coarser granularity than City. So, if City is excepted, County and State
+are excepted too. If you apply the exception to the State attribute, it
+is the only attribute filter that is excepted.
+
+## Syntax
+
+\`\`\`
+SELECT ... WITHOUT PARENT FILTER EXCEPT Attribute1,...
+\`\`\`
+
+\`\`\`
+SELECT ... WITHOUT PF EXCEPT Attribute1,...
+\`\`\`
+
+## Example 1
+
+In the table below, you can see how the WITHOUT PARENT FILTER EXCEPT
+keyword works with the State-County-City hierarchy.
+
+
+| Definition                          | visualization Filter    | Metric Value |
+|-------------------------------------|------------------|--------------|
+| \`SELECT M1\`                         | (none)           | 1000         |
+| \`SELECT M1\`                         |  F1: County = X | 600          |
+| \`SELECT M1 WITHOUT PF\`              |  F1: County = X | 1000         |
+| \`SELECT M1 WITHOUT PF EXCEPT City\`  |  F1: County = X | 600          |
+| \`SELECT M1 WITHOUT PF EXCEPT State\` |  F1: County = X | 1000         |
+| \`SELECT M1 WITHOUT PF EXCEPT State\` |  F1: State = Y  | 550          |
+
+
+-   In the above example in the third row, the WITHOUT PARENT FILTER
+    removes all parent filters from the metric, so COUNTY = X is not
+    applied. The returned results match the unfiltered version of the
+    metric in the first row.
+-   In the fourth row, City is excepted. Since County has a coarser grain than City, the parent visualization filter (County = X) is applied.
+-   In the fifth row, the excepted filter is State. However, the visualization
+    filter is at the County attribute level, which is finer than State.
+    Therefore, the filter is not applied, and the results match the
+    unfiltered version in the first row.
+-   In the fifth row, the excepted filter is State, which matches the
+    visualization filter. So, the results are filtered.
+
+## Example 2
+
+In the table below, you can see how the WITHOUT PARENT
+FILTER EXCEPT keyword affects the filtered version of the visualization.
+
+
+| Definition               | Visualization Filter            | Metric Value |
+|--------------------------|--------------------------|--------------|
+| \`SELECT M1\`              | (none)                   | 500          |
+| \`SELECT M1\`              |  F1: Group = X          | 350          |
+| \`SELECT M1\`              |  F1: Group =            | 250          |
+|                          | X; F2: Priority is Y    |              |
+| \`SELECT M1 WITHOUT PARENT FILTER EXCEPT Group\`   |  F1: Group = X; F2: Priority is Y           | 350          |
+
+
+In the above example in the fourth row, the
+WITHOUT PARENT FILTER EXCEPT removes all parent filters from the metric,
+except for one: Group, so the Priority filter is not applied to the
+metric. The generated metric value equates to the value generated in the
+version in the second row.
+
+
+## Example 3
+
+  |Definition                                                                |  visualization Filter|
+  |---------------------------------------------------------------------------|---------------|
+  |\`SELECT (SELECT M1 WITHOUT PF EXCEPT Date) WHERE (SELECT M2 BY Date) > Y\`  | Group = X |
+
+
+-   M2 is filtered by group.
+-   M1 is not filtered by group, only by the numeric range filter in the
+    \`WHERE\` part.
+
+## Example 4
+
+| Definition                                          | Visualization Filter |
+|-----------------------------------------------------|---------------|
+| \`SELECT (SELECT M1 WITHOUT PF EXCEPT Date) WHERE (SELECT M2 BY Date) > Y\`    | Group = X  Date = Z   |
+
+-   M2 is filtered by group, date.
+-   M1 is filtered by date and the numeric range in the \`WHERE\` part.`;

package/esm/docs/en/docs/create-metrics/maql/filters/overriding-parent/without-parent-filter.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "Removes parent filters from being applied to the metric. All parent\nfilters specified in visualization, dashboards, and any metrics in which this\nmetric is nested are ignored.\n\nThis clause can be shortened to WITHOUT PF.\n\n**Example**\n\nIn the table below, you can see how the WITHOUT PARENT FILTER clause\naffects the filtered version of the visualization.\n\n\n| Definition                        | Visualization Filter   | Metric Value |\n|-----------------------------------|-----------------|--------------|\n| `SELECT M1`                       | (none)          | 500          |\n| `SELECT M1`                       |  F1: Group = X | 350          |\n| `SELECT M1 WITHOUT PARENT FILTER` |  F1: Group = X | 500          |\n\n\nSince the metric in the third row removes the parent filter in the\nvisualization, the returned value matches the calculation when no visualization filter\nis applied in the first row.\n\n## Syntax\n\n```\nSELECT ... WITHOUT PARENT FILTER\n```\n\n```\nSELECT ... WITHOUT PF\n```";
+//# sourceMappingURL=without-parent-filter.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/filters/overriding-parent/without-parent-filter.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"without-parent-filter.d.ts","sourceRoot":"","sources":["../../../../../../../../src/docs/en/docs/create-metrics/maql/filters/overriding-parent/without-parent-filter.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,6/BA+Bb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/filters/overriding-parent/without-parent-filter.js

@@ -0,0 +1,33 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `Removes parent filters from being applied to the metric. All parent
+filters specified in visualization, dashboards, and any metrics in which this
+metric is nested are ignored.
+
+This clause can be shortened to WITHOUT PF.
+
+**Example**
+
+In the table below, you can see how the WITHOUT PARENT FILTER clause
+affects the filtered version of the visualization.
+
+
+| Definition                        | Visualization Filter   | Metric Value |
+|-----------------------------------|-----------------|--------------|
+| \`SELECT M1\`                       | (none)          | 500          |
+| \`SELECT M1\`                       |  F1: Group = X | 350          |
+| \`SELECT M1 WITHOUT PARENT FILTER\` |  F1: Group = X | 500          |
+
+
+Since the metric in the third row removes the parent filter in the
+visualization, the returned value matches the calculation when no visualization filter
+is applied in the first row.
+
+## Syntax
+
+\`\`\`
+SELECT ... WITHOUT PARENT FILTER
+\`\`\`
+
+\`\`\`
+SELECT ... WITHOUT PF
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/for-each.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# For Each\nDisplay all values for a given label. For datetime attributes continuous series of values is generated.\n\n\n### MAQL Syntax\n\n```\nSELECT \u2026 BY \u2026 FOR EACH {attribute/label}, {attribute/label}, \u2026  FOR PREVIOUS \u2026 WHERE \u2026 HAVING \u2026 USING \u2026 WITHOUT PF \u2026\n```\n\nExample:\n\n```\nSELECT SUM({fact/lineitem.l_extendedprice}) FOR EACH {attribute/o_orderdatetime.month}, {attribute/part.p_brand}\n```\n";
+//# sourceMappingURL=for-each.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/for-each.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"for-each.d.ts","sourceRoot":"","sources":["../../../../../../src/docs/en/docs/create-metrics/maql/for-each.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,mcAenB,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/for-each.js

@@ -0,0 +1,17 @@
+// (C) 2023-2026 GoodData Corporation
+export const content = `# For Each
+Display all values for a given label. For datetime attributes continuous series of values is generated.
+
+
+### MAQL Syntax
+
+\`\`\`
+SELECT … BY … FOR EACH {attribute/label}, {attribute/label}, …  FOR PREVIOUS … WHERE … HAVING … USING … WITHOUT PF …
+\`\`\`
+
+Example:
+
+\`\`\`
+SELECT SUM({fact/lineitem.l_extendedprice}) FOR EACH {attribute/o_orderdatetime.month}, {attribute/part.p_brand}
+\`\`\`
+`;

package/esm/docs/en/docs/create-metrics/maql/logical-operators/and.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# AND\nAND logical operator works in the following way:\n\n-   If both expressions are true (e.g. not FALSE and not NULL), then the\n    result is true.\n-   In all other cases, the result is false.\n\nIf you combine filters using AND, both filters are applied when\ncomputing the metric.\n\n## Examples:\n\n```\nSELECT {metric/payment} WHERE {label/date.year} = \"2006\" AND {label/date.month} = \"5\"\n```\n\nWhile OR combines filters in a way that allows more data to pass through\nvisualization computations, AND restricts, or limits, the amount of data that\nis used in computations.\n\nConsider the case where our metric has a filter that serves to include\nall data from 2006 as well as data from the first four months of 2007.\nAdding an additional AND clause onto the metric definition limits the\ndata that is used in the metric's computations because now there are\nmore conditions than before that data must meet in order to be included in computations.\n\nIn the following example, payments must come from 2006 or the first four\nmonths of 2007 to be included in metric computations. They must also be\ngreater than $10,000.\n\n```\nSELECT SUM({metric/payment}) WHERE ({label/date.year} = \"2006\" OR {label/date.month} IN (\"2007-01\", \"2007-02\", \"2007-03\", \"2007-04\")) AND {metric/payment} > 10000\n```\n\nPayment values that come from 2006 or the first four months of 2007 but\nare less than 10,000 will be excluded.";
+//# sourceMappingURL=and.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/logical-operators/and.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"and.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/logical-operators/and.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,m6CAmCmB,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/logical-operators/and.js

@@ -0,0 +1,37 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# AND
+AND logical operator works in the following way:
+
+-   If both expressions are true (e.g. not FALSE and not NULL), then the
+    result is true.
+-   In all other cases, the result is false.
+
+If you combine filters using AND, both filters are applied when
+computing the metric.
+
+## Examples:
+
+\`\`\`
+SELECT {metric/payment} WHERE {label/date.year} = "2006" AND {label/date.month} = "5"
+\`\`\`
+
+While OR combines filters in a way that allows more data to pass through
+visualization computations, AND restricts, or limits, the amount of data that
+is used in computations.
+
+Consider the case where our metric has a filter that serves to include
+all data from 2006 as well as data from the first four months of 2007.
+Adding an additional AND clause onto the metric definition limits the
+data that is used in the metric's computations because now there are
+more conditions than before that data must meet in order to be included in computations.
+
+In the following example, payments must come from 2006 or the first four
+months of 2007 to be included in metric computations. They must also be
+greater than $10,000.
+
+\`\`\`
+SELECT SUM({metric/payment}) WHERE ({label/date.year} = "2006" OR {label/date.month} IN ("2007-01", "2007-02", "2007-03", "2007-04")) AND {metric/payment} > 10000
+\`\`\`
+
+Payment values that come from 2006 or the first four months of 2007 but
+are less than 10,000 will be excluded.`;

package/esm/docs/en/docs/create-metrics/maql/logical-operators/not.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# NOT\nNOT is a logical operator that negates the filter it precedes.\n\nIf you specify a filter and precede it with NOT, then everything that is\nspecified by the filter is excluded from the computation.\n\n**Example:**\n\n```\nSELECT {metric/profit} WHERE NOT ({label/date_ordered.year} = \"2006\" AND {label/date_ordered.month} = \"5\")\n```";
+//# sourceMappingURL=not.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/logical-operators/not.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"not.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/logical-operators/not.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,6VAUb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/logical-operators/not.js

@@ -0,0 +1,12 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# NOT
+NOT is a logical operator that negates the filter it precedes.
+
+If you specify a filter and precede it with NOT, then everything that is
+specified by the filter is excluded from the computation.
+
+**Example:**
+
+\`\`\`
+SELECT {metric/profit} WHERE NOT ({label/date_ordered.year} = "2006" AND {label/date_ordered.month} = "5")
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/logical-operators/or.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# OR\nOR logical operator works in the following way:\n\n-   If either expression is true, then the result is true.\n-   If both expressions are false, then the result is false.\n\n## Examples\n\nIn the following example, all metric values associated with the years 2006 and 2005 will be returned.\n\n```\nSELECT {metric/payment} WHERE {label/date_ordered.year} = \"2006\" OR {label/date_ordered.year} = \"2005\"\n```\n\n`OR` can also be used to combine two different types of filters. Consider\nthe case where you want to return the total of all payments from the\nyear 2006 and the first four months of 2007:\n\n```\nSELECT SUM({metric/payment}) WHERE {label/date_ordered.year} = \"2006\" OR {label/date_ordered.month} IN (\"2007-01\", \"2007-02\", \"2007-03\", \"2007-04\")\n```";
+//# sourceMappingURL=or.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/logical-operators/or.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"or.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/logical-operators/or.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,kxBAoBb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/logical-operators/or.js

@@ -0,0 +1,22 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# OR
+OR logical operator works in the following way:
+
+-   If either expression is true, then the result is true.
+-   If both expressions are false, then the result is false.
+
+## Examples
+
+In the following example, all metric values associated with the years 2006 and 2005 will be returned.
+
+\`\`\`
+SELECT {metric/payment} WHERE {label/date_ordered.year} = "2006" OR {label/date_ordered.year} = "2005"
+\`\`\`
+
+\`OR\` can also be used to combine two different types of filters. Consider
+the case where you want to return the total of all payments from the
+year 2006 and the first four months of 2007:
+
+\`\`\`
+SELECT SUM({metric/payment}) WHERE {label/date_ordered.year} = "2006" OR {label/date_ordered.month} IN ("2007-01", "2007-02", "2007-03", "2007-04")
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/maql-and-multidimensionality.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# MAQL and Multidimensionality\nMultidimensionality is a fundamental principle of GoodData's MAQL (Multi-Dimension Analytical Query Language).\n\nMultidimensional modeling works with the concepts of facts and dimensions meaning that MAQL metrics are context aware.\n\nMetrics are sliced by dimension context that does not need to be specified in the MAQL expressions themselves. This multidimensional capability is one of the features that sets MAQL apart from SQL.\n\n## Examples of Multidimensionality\n\nIn this section, we will use several examples to show you how MAQL works with dimensionality.\n\n### Example 1\n\nIn this example, we created a SUM metric to display *amount sold* of a particular product.\n\n```\nSELECT SUM({fact/amount})\n```\n\nYou can apply additional *dimensions* (in this case *Product* and *Year*) to this simple metric to break down the metric:\n\n\n  |Metric       | Dimensionality |  What it returns (business meaning)|\n  |-------------| ---------------- |--------------------------------------------|\n  |Amount Sold   |(empty)        |  total all-time sales (1 row)|\n  |Amount Sold   |Product        |  all-time sales for each sold product|\n  |Amount Sold   |Product, Year   | sales for each existing year and product combination|\n\n### Example 2\n\n```\nSELECT SUM({fact/amount}) WHERE SUM({fact/amount}) > 25\n```\n\nThe dimensionality of the result and dimensionality of the filter are the same and defined by the dimensionality of the visualization.\n\n\n  |Metric            |Dimensionality   |What it returns (business meaning)|\n  |----------------- |---------------- |---------------------------------------------|\n  |Amount Sold 25+   |(empty)          |Total sales of everything every  time (if the total is >25).|\n  |Amount Sold 25+   |Product          |Total sales of each product if sales for that product is >25.|\n  |Amount Sold 25+   |Product, Year    |Sales of each product each year if at least 25 pieces of that product were sold within that year.|\n\n### Example 3\n\n```\nSELECT SUM({fact/amount}) \n    WHERE (SELECT SUM({fact/quantity}) BY {attribute/product} ALL OTHER) > 25\n```\n\nThe dimensionality of the main (result) metric is different from dimensionality of the filtering metric. The dimensionality of the filtering metric is locked to Product.\n\n\n  |Metric            |Dimensionality   |What it returns (business meaning)|\n  |----------------- |---------------- |---------------------------------------------|\n  |Amount Sold 25+   |(empty)          |Total sales of products with more than 25 sold items.|\n  |Amount Sold 25+  | Product          |Total sales of each product with more than 25 sold items.|\n  |Amount Sold 25+  | Product, Year    |Sales of each product and year for products with more than 25 sold items.|";
+//# sourceMappingURL=maql-and-multidimensionality.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/maql-and-multidimensionality.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"maql-and-multidimensionality.d.ts","sourceRoot":"","sources":["../../../../../../src/docs/en/docs/create-metrics/maql/maql-and-multidimensionality.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,mvFAyD+F,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/maql-and-multidimensionality.js

@@ -0,0 +1,59 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# MAQL and Multidimensionality
+Multidimensionality is a fundamental principle of GoodData's MAQL (Multi-Dimension Analytical Query Language).
+
+Multidimensional modeling works with the concepts of facts and dimensions meaning that MAQL metrics are context aware.
+
+Metrics are sliced by dimension context that does not need to be specified in the MAQL expressions themselves. This multidimensional capability is one of the features that sets MAQL apart from SQL.
+
+## Examples of Multidimensionality
+
+In this section, we will use several examples to show you how MAQL works with dimensionality.
+
+### Example 1
+
+In this example, we created a SUM metric to display *amount sold* of a particular product.
+
+\`\`\`
+SELECT SUM({fact/amount})
+\`\`\`
+
+You can apply additional *dimensions* (in this case *Product* and *Year*) to this simple metric to break down the metric:
+
+
+  |Metric       | Dimensionality |  What it returns (business meaning)|
+  |-------------| ---------------- |--------------------------------------------|
+  |Amount Sold   |(empty)        |  total all-time sales (1 row)|
+  |Amount Sold   |Product        |  all-time sales for each sold product|
+  |Amount Sold   |Product, Year   | sales for each existing year and product combination|
+
+### Example 2
+
+\`\`\`
+SELECT SUM({fact/amount}) WHERE SUM({fact/amount}) > 25
+\`\`\`
+
+The dimensionality of the result and dimensionality of the filter are the same and defined by the dimensionality of the visualization.
+
+
+  |Metric            |Dimensionality   |What it returns (business meaning)|
+  |----------------- |---------------- |---------------------------------------------|
+  |Amount Sold 25+   |(empty)          |Total sales of everything every  time (if the total is \>25).|
+  |Amount Sold 25+   |Product          |Total sales of each product if sales for that product is \>25.|
+  |Amount Sold 25+   |Product, Year    |Sales of each product each year if at least 25 pieces of that product were sold within that year.|
+
+### Example 3
+
+\`\`\`
+SELECT SUM({fact/amount}) 
+    WHERE (SELECT SUM({fact/quantity}) BY {attribute/product} ALL OTHER) > 25
+\`\`\`
+
+The dimensionality of the main (result) metric is different from dimensionality of the filtering metric. The dimensionality of the filtering metric is locked to Product.
+
+
+  |Metric            |Dimensionality   |What it returns (business meaning)|
+  |----------------- |---------------- |---------------------------------------------|
+  |Amount Sold 25+   |(empty)          |Total sales of products with more than 25 sold items.|
+  |Amount Sold 25+  | Product          |Total sales of each product with more than 25 sold items.|
+  |Amount Sold 25+  | Product, Year    |Sales of each product and year for products with more than 25 sold items.|`;

package/esm/docs/en/docs/create-metrics/maql/math/abs.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# ABS\nThe absolute value function (ABS) returns an absolute value of a number\n(e.g., Revenue) as a positive number:\n\n-   positive inputs will remain unchanged\n-   negative inputs will be rendered positive\n\n## Syntax\n\n```\nSELECT ABS(\u2026)\nSELECT ABS(number)\nSELECT ABS(metric)\n```\n\n## Examples\n\n```\nSELECT ABS(-5) returns the value \"5\"\nSELECT ABS(10) returns the value \"10\"\nSELECT ABS(({metric/total_amount})-(SELECT {metric/total_amount} WITHOUT PF))\n```";
+//# sourceMappingURL=abs.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/math/abs.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"abs.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/math/abs.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,seAqBb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/math/abs.js

@@ -0,0 +1,23 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# ABS
+The absolute value function (ABS) returns an absolute value of a number
+(e.g., Revenue) as a positive number:
+
+-   positive inputs will remain unchanged
+-   negative inputs will be rendered positive
+
+## Syntax
+
+\`\`\`
+SELECT ABS(…)
+SELECT ABS(number)
+SELECT ABS(metric)
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT ABS(-5) returns the value "5"
+SELECT ABS(10) returns the value "10"
+SELECT ABS(({metric/total_amount})-(SELECT {metric/total_amount} WITHOUT PF))
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/math/arithmetic-operations.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# Arithmetic Operations\nPredefined metrics can be manipulated with any basic arithmetic\noperation: addition (+), subtraction (-), multiplication (*), and\ndivision (/).\n\nBy using numerical variables, you can also add dynamic values into your arithmetic operations.\n\n## Adding, Subtracting, Multiplying, and Dividing\n\nAdd, subtract, multiply, or divide predefined metrics.\n\n## Syntax\n\n```\nSELECT metric1 + metric2\nSELECT metric1 - metric2\nSELECT metric1 * metric2\nSELECT metric1 / metric2\n```\n\n## Examples\n\n```\nSELECT {metric/expenses} + {metric/salary}\nSELECT {metric/revenue} - {metric/cost}\nSELECT {metric/profit} * 0.03\nSELECT {metric/new_revenue} / {metric/revenue_last_year}\n```";
+//# sourceMappingURL=arithmetic-operations.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/math/arithmetic-operations.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"arithmetic-operations.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/math/arithmetic-operations.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,0sBA2Bb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/math/arithmetic-operations.js

@@ -0,0 +1,29 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# Arithmetic Operations
+Predefined metrics can be manipulated with any basic arithmetic
+operation: addition (+), subtraction (-), multiplication (*), and
+division (/).
+
+By using numerical variables, you can also add dynamic values into your arithmetic operations.
+
+## Adding, Subtracting, Multiplying, and Dividing
+
+Add, subtract, multiply, or divide predefined metrics.
+
+## Syntax
+
+\`\`\`
+SELECT metric1 + metric2
+SELECT metric1 - metric2
+SELECT metric1 * metric2
+SELECT metric1 / metric2
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT {metric/expenses} + {metric/salary}
+SELECT {metric/revenue} - {metric/cost}
+SELECT {metric/profit} * 0.03
+SELECT {metric/new_revenue} / {metric/revenue_last_year}
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/math/ceiling.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# CEILING\nThe CEILING function rounds an input value to the nearest integer that\nis greater than it.\n\n## Syntax\n\n```\nSELECT CEILING(\u2026)\nCEILING(constant)\nCEILING(fact)\nCEILING(metric)\nCEILING(metric_expression)\n```\n\n## Examples\n\n```\nSELECT CEILING(12.2) = 13\nSELECT CEILING(12.7) = 13\n```";
+//# sourceMappingURL=ceiling.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/math/ceiling.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ceiling.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/math/ceiling.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,4TAmBb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/math/ceiling.js

@@ -0,0 +1,21 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# CEILING
+The CEILING function rounds an input value to the nearest integer that
+is greater than it.
+
+## Syntax
+
+\`\`\`
+SELECT CEILING(…)
+CEILING(constant)
+CEILING(fact)
+CEILING(metric)
+CEILING(metric_expression)
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT CEILING(12.2) = 13
+SELECT CEILING(12.7) = 13
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/math/exp.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# EXP\nThe exponential function EXP returns *e* raised to the power of a number\n(e.g., Annual rate).\n\nAs the inverse of the LN(*n*) function, EXP(*n*) returns the value of\nthe constant e, 2.71828182845904, raised to the power of the positive\nreal number, n.\n\nEXP( ) takes as arguments any numeric data, including metrics, metrics\nexpressions, and constants.\n\n## Syntax\n\n```\nEXP(\u2026)\nEXP(number)\n```\n\n## Examples\n\n```\nSELECT EXP(10)\nSELECT EXP(1/12)\nSELECT EXP(1.5)\nSELECT EXP(SUM({fact/amount}))\n```";
+//# sourceMappingURL=exp.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/math/exp.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"exp.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/math/exp.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,mhBAyBb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/math/exp.js

@@ -0,0 +1,27 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# EXP
+The exponential function EXP returns *e* raised to the power of a number
+(e.g., Annual rate).
+
+As the inverse of the LN(*n*) function, EXP(*n*) returns the value of
+the constant e, 2.71828182845904, raised to the power of the positive
+real number, n.
+
+EXP( ) takes as arguments any numeric data, including metrics, metrics
+expressions, and constants.
+
+## Syntax
+
+\`\`\`
+EXP(…)
+EXP(number)
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT EXP(10)
+SELECT EXP(1/12)
+SELECT EXP(1.5)
+SELECT EXP(SUM({fact/amount}))
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/math/floor.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# FLOOR\nThe FLOOR function rounds an input value to the nearest integer that is\nless than it.\n\n## Syntax\n\n```\nSELECT FLOOR(\u2026)\nFLOOR(constant)\nFLOOR(fact)\nFLOOR(metric)\nFLOOR(metric_expression)\n```\n\n## Examples\n\n```\nSELECT FLOOR(12.2) = 12\nSELECT FLOOR(12.7) = 12\n```";
+//# sourceMappingURL=floor.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/math/floor.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"floor.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/math/floor.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,uSAmBb,CAAC"}

package/esm/docs/en/docs/create-metrics/maql/math/floor.js

@@ -0,0 +1,21 @@
+// (C) 2021-2026 GoodData Corporation
+export const content = `# FLOOR
+The FLOOR function rounds an input value to the nearest integer that is
+less than it.
+
+## Syntax
+
+\`\`\`
+SELECT FLOOR(…)
+FLOOR(constant)
+FLOOR(fact)
+FLOOR(metric)
+FLOOR(metric_expression)
+\`\`\`
+
+## Examples
+
+\`\`\`
+SELECT FLOOR(12.2) = 12
+SELECT FLOOR(12.7) = 12
+\`\`\``;

package/esm/docs/en/docs/create-metrics/maql/math/greatest.d.ts

@@ -0,0 +1,2 @@
+export declare const content = "# GREATEST\nThe GREATEST function identifies the highest value from a selection of\nfacts or metrics within one row.\n\n## Syntax\n\n```\nSELECT GREATEST(\u2026, \u2026, \u2026)\nSELECT GREATEST(fact, fact)\nSELECT GREATEST(metric, metric)\nSELECT GREATEST(fact, metric, metric, fact)\n```";
+//# sourceMappingURL=greatest.d.ts.map

package/esm/docs/en/docs/create-metrics/maql/math/greatest.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"greatest.d.ts","sourceRoot":"","sources":["../../../../../../../src/docs/en/docs/create-metrics/maql/math/greatest.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,OAAO,sSAWb,CAAC"}