Revert "docs(schema): replace camel-case properties with snake-case"

This reverts commit 50cfd04.

Author: hassankhan

docs/content/Schema/Reference/cube.mdx

@@ -228,13 +228,13 @@ cube(`Contacts`, {
 
 ## Parameters
 
-### <--{"id" : "Parameters"}--> data_source
+### <--{"id" : "Parameters"}--> dataSource
 
-Each cube in schema can have its own `data_source` name to support scenarios
+Each cube in schema can have its own `dataSource` name to support scenarios
 where data should be fetched from multiple databases. The value of the
-`data_source` parameter will be passed to the
+`dataSource` parameter will be passed to the
 [`driverFactory()`][ref-config-driverfactory] function as part of the `context`
-parameter. By default, each cube has a `default` value for its `data_source`; to
+parameter. By default, each cube has a `default` value for its `dataSource`; to
 override it you can use:
 
 <CodeTabs>
@@ -243,7 +243,7 @@ override it you can use:
 cube(`OrderFacts`, {
   sql: `SELECT * FROM orders`,
 
-  data_source: `prod_db`,
+  dataSource: `prod_db`,
 });
 ```
 
@@ -364,21 +364,21 @@ cube(`ExtendedOrderFacts`, {
 });
 ```
 
-### <--{"id" : "Parameters"}--> refresh_key
+### <--{"id" : "Parameters"}--> refreshKey
 
-Cube's caching layer uses `refresh_key` queries to get the current version of
+Cube's caching layer uses `refreshKey` queries to get the current version of
 content for a specific cube. If a query result changes, Cube will invalidate all
 queries that rely on that cube.
 
-The default values for `refresh_key` are
+The default values for `refreshKey` are
 
 - `every: '2 minute'` for BigQuery, Athena, Snowflake, and Presto.
 - `every: '10 second'` for all other databases.
 
 Refresh key of a query is a concatenation of all cubes refresh keys involved in
 query. For rollup queries pre-aggregation table name is used as a refresh key.
 
-You can set up a custom refresh check SQL by changing `refresh_key` property.
+You can set up a custom refresh check SQL by changing `refreshKey` property.
 Often, a `MAX(updated_at_timestamp)` for OLTP data is a viable option, or
 examining a metadata table for whatever system is managing the data to see when
 it last ran. timestamp in that case.
@@ -389,10 +389,10 @@ it last ran. timestamp in that case.
 cube(`OrderFacts`, {
   sql: `SELECT * FROM orders`,
 
-  // With this refresh_key Cube will only refresh the data if
+  // With this refreshKey Cube will only refresh the data if
   // the value of previous MAX(updated_at_timestamp) changed
-  // By default Cube will check this refresh_key every 10 seconds
-  refresh_key: {
+  // By default Cube will check this refreshKey every 10 seconds
+  refreshKey: {
     sql: `SELECT MAX(updated_at_timestamp) FROM orders`,
   },
 });
@@ -408,15 +408,15 @@ cubes:
 
 </CodeTabs>
 
-You can use interval based `refresh_key`. For example:
+You can use interval based `refreshKey`. For example:
 
 <CodeTabs>
 
 ```javascript
 cube(`OrderFacts`, {
   sql: `SELECT * FROM orders`,
 
-  refresh_key: {
+  refreshKey: {
     every: `1 hour`,
   },
 });
@@ -443,7 +443,7 @@ For example:
 ```javascript
 cube(`OrderFacts`, {
   sql: `SELECT * FROM orders`,
-  refresh_key: {
+  refreshKey: {
     every: '30 5 * * 5',
     timezone: 'America/Los_Angeles',
   },
@@ -471,21 +471,21 @@ with support for seconds.
 
 </WarningBox>
 
-Such `refresh_key` is just a syntactic sugar over `refresh_key` SQL. It's
-guaranteed that `refresh_key` change its value at least once during `every`
+Such `refreshKey` is just a syntactic sugar over `refreshKey` SQL. It's
+guaranteed that `refreshKey` change it's value at least once during `every`
 interval. It will be converted to appropriate SQL select which value will change
-over time based on interval value. Values of interval based `refresh_key` are
+over time based on interval value. Values of interval based `refreshKey` are
 tried to be checked ten times within defined interval but not more than once per
 `1 second` and not less than once per `5 minute`. For example if interval is
-`10 minute` it's `refresh_key_renewal_threshold` will be 60 seconds and
-generated `refresh_key` SQL (Postgres) would be:
+`10 minute` it's `refreshKeyRenewalThreshold` will be 60 seconds and generated
+`refreshKey` SQL (Postgres) would be:
 
 ```sql
 SELECT FLOOR(EXTRACT(EPOCH FROM NOW()) / 600)
 ```
 
-For `5 second` interval `refresh_key_renewal_threshold` will be just 1 second
-and SQL will be:
+For `5 second` interval `refreshKeyRenewalThreshold` will be just 1 second and
+SQL will be:
 
 ```sql
 SELECT FLOOR(EXTRACT(EPOCH FROM NOW()) / 5)
@@ -520,7 +520,7 @@ SELECT FLOOR(EXTRACT(EPOCH FROM NOW()) / 5)
 └───────────────────────── second (0 - 59, optional)
 ```
 
-### <--{"id" : "Parameters"}--> rewrite_queries
+### <--{"id" : "Parameters"}--> rewriteQueries
 
 Set this flag to true if you want Cube to rewrite your queries after final SQL
 has been generated. This may be helpful to apply filter pushdown optimizations
@@ -530,7 +530,7 @@ or reduce unnecessary query nesting. For example:
 
 ```javascript
 cube(`Tickets`, {
-  rewrite_queries: true,
+  rewriteQueries: true,
 });
 ```
 
@@ -602,9 +602,9 @@ cube(`Companies`, {
 });
 ```
 
-### <--{"id" : "Parameters"}--> sql_alias
+### <--{"id" : "Parameters"}--> sqlAlias
 
-Use `sql_alias` when auto-generated cube alias prefix is too long and truncated
+Use `sqlAlias` when auto-generated cube alias prefix is too long and truncated
 by DB such as Postgres:
 
 <CodeTabs>
@@ -613,7 +613,7 @@ by DB such as Postgres:
 cube(`OrderFacts`, {
   sql: `SELECT * FROM orders`,
 
-  sql_alias: `ofacts`,
+  sqlAlias: `ofacts`,
 
   // ...
 });
@@ -628,7 +628,7 @@ cubes:
 
 </CodeTabs>
 
-It'll generate aliases for members such as `ofacts__count`. `sql_alias` affects
+It'll generate aliases for members such as `ofacts__count`. `sqlAlias` affects
 all member names including pre-aggregation table names.
 
 ### <--{"id" : "Parameters"}--> title
@@ -705,7 +705,8 @@ cube(`OrderFacts`, {
 cubes:
   - name: OrderFacts
     sql: >
-      SELECT * FROM orders WHERE {FILTER_PARAMS.OrderFacts.date.filter('date')}
+      SELECT * FROM orders
+      WHERE {FILTER_PARAMS.OrderFacts.date.filter('date')}
     measures:
       - name: count
         type: count

docs/content/Schema/Reference/dimensions.mdx

@@ -11,8 +11,8 @@ redirect_from:
 ---
 
 The `dimensions` property contains a set of dimensions. You can think about a
-dimension as an attribute related to a measure, e.g. the measure `user_count`
-can have dimensions like `country`, `age`, `occupation`, etc.
+dimension as an attribute related to a measure, e.g. the measure `userCount` can
+have dimensions like `country`, `age`, `occupation`, etc.
 
 Any dimension should have the following properties: `name`, `sql` and `type`.
 
@@ -209,7 +209,7 @@ cubes:
 
 </CodeTabs>
 
-### <--{"id" : "Parameters"}--> primary_key
+### <--{"id" : "Parameters"}--> primaryKey
 
 Specify which dimension is a primary key for a cube. The default value is
 `false`.
@@ -218,7 +218,7 @@ A primary key is used to make [joins][ref-schema-ref-joins] work properly.
 
 <WarningBox>
 
-Setting `primary_key` to `true` will change the default value of `shown`
+Setting `primaryKey` to `true` will change the default value of `shown`
 parameter to `false`. If you still want `shown` to be `true`, set it manually.
 
 </WarningBox>
@@ -231,7 +231,7 @@ cube('Products', {
     id: {
       sql: `id`,
       type: `number`,
-      primary_key: true,
+      primaryKey: true,
     },
   },
 });
@@ -249,7 +249,7 @@ cubes:
 
 </CodeTabs>
 
-### <--{"id" : "Parameters"}--> propagate_filters_to_sub_query
+### <--{"id" : "Parameters"}--> propagateFiltersToSubQuery
 
 When this statement is set to `true`, the filters applied to the query will be
 passed to the [subquery][self-subquery].
@@ -262,8 +262,8 @@ cube('Products', {
     users_count: {
       sql: `${Users.count}`,
       type: `number`,
-      sub_query: true,
-      propagate_filters_to_sub_query: true,
+      subQuery: true,
+      propagateFiltersToSubQuery: true,
     },
   },
 });
@@ -276,8 +276,8 @@ cubes:
       - name: users_count
         sql: "{Users.count}"
         type: number
-        sub_query: true
-        propagate_filters_to_sub_query: true
+        subQuery: true
+        propagateFiltersToSubQuery: true
 ```
 
 </CodeTabs>
@@ -331,10 +331,10 @@ cube(`Orders`, {
 });
 ```
 
-### <--{"id" : "Parameters"}--> sub_query
+### <--{"id" : "Parameters"}--> subQuery
 
-The `sub_query` statement allows you to reference a measure in a dimension. It's
-an advanced concept; you can learn more about it [here][ref-subquery].
+The `subQuery` statement allows you to reference a measure in a dimension. It's
+an advanced concept and you can learn more about it [here][ref-subquery].
 
 <CodeTabs>
 
@@ -344,7 +344,7 @@ cube('Products', {
     users_count: {
       sql: `${Users.count}`,
       type: `number`,
-      sub_query: true,
+      subQuery: true,
     },
   },
 });
@@ -357,7 +357,7 @@ cubes:
       - name: usersCount
         sql: "{Users.count}"
         type: number
-        sub_query: true
+        subQuery: true
 ```
 
 </CodeTabs>