The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:
TypeScript analyticsbibusiness-intelligencebusinessintelligenceclojuredashboarddatadata-analysisdata-visualizationdatabasemetabasemysqlpostgrespostgresqlreportingslacksql-editorvisualization
Run Codespell on `docs/` (#65925)
Cam Saulaf139fd0038b
diff --git a/.codespellignore b/.codespellignorenew file mode 100644index 00000000000..03653a4e5e4--- /dev/null+++ b/.codespellignore@@ -0,0 +1,23 @@+Brite+afterAll+ags+altho+cancelation+cancelations+datas+edn+eduction+hasTables+horizontalX+horizontalY+juxt+methodd+notIn+pass-thru+ser+serieses+sortings+trs+trsn+tru+trundiff --git a/.codespellrc b/.codespellrcnew file mode 100644index 00000000000..5e5d63027d1--- /dev/null+++ b/.codespellrc@@ -0,0 +1,3 @@+[codespell]+skip = *.csv,*.edn,*.geojson,*.json,*.tsv,*.xml,docs/developers-guide/drivers/driver-tests.md,docs/developers-guide/e2e-tests.md,docs/questions/query-builder/expressions-list.md,docs/questions/visualizations/country-codes.md,e2e/test/scenarios/admin/i18n/content-translation/constants.ts,frontend/src/cljs,frontend/src/metabase/querying/expressions/tokenizer/lezer.js,frontend/src/metabase/static-viz/constants/char-sizes.ts,frontend/src/metabase/visualizations/lib/mapping_codes.ts,modules/drivers/mongo/src/metabase/driver/mongo/operators.clj+ignore-words = .codespellignorediff --git a/.github/workflows/codespell.yml b/.github/workflows/codespell.ymlnew file mode 100644index 00000000000..9422e3de93e--- /dev/null+++ b/.github/workflows/codespell.yml@@ -0,0 +1,19 @@+name: Codespell++on:+ push:+ branches:+ - 'master'+ - 'release-**'+ pull_request:++jobs:+ codespell:+ runs-on: ubuntu-latest+ steps:+ - uses: actions/checkout@v3+ - uses: codespell-project/actions-codespell@v1+ with:+ # keep this list in sync with the list in `mage/src/mage/codespell.yml`+ path: >-+ docsdiff --git a/bb.edn b/bb.ednindex 67dd8e667a9..7e594e2df92 100644--- a/bb.edn+++ b/bb.edn@@ -83,6 +83,18 @@:requires [[mage.check]]:task (task! (mage.check/check (:arguments parsed)))}+ codespell+ {:doc "Check for misspellings in the source code."+ :examples [["./bin/mage codespell"]]+ :requires [[mage.codespell]]+ :task (task! (mage.codespell/codespell (:arguments parsed)))}++ codespell-interactive+ {:doc "Check for misspellings in the source code, and interactively prompt to fix them."+ :examples [["./bin/mage codespell-interactive"]]+ :requires [[mage.codespell]]+ :task (task! (mage.codespell/codespell-interactive (:arguments parsed)))}+start-maildev{:doc "Start Maildev":examples [["./bin/mage start-maildev -h" "print help for start-maildev"]]diff --git a/docs/cloud/how-billing-works.md b/docs/cloud/how-billing-works.mdindex 10b13674e60..9eae793119b 100644--- a/docs/cloud/how-billing-works.md+++ b/docs/cloud/how-billing-works.md@@ -79,7 +79,7 @@ For example, say you're running two Metabase instances, A and B, that both use tThen the number of user accounts would total 8 for that day.-If you're on Metabase Cloud, counting active users works the same: each day we count the maxium number of user accounts at any one time over the previous 36 hours.+If you're on Metabase Cloud, counting active users works the same: each day we count the maximum number of user accounts at any one time over the previous 36 hours.We refresh the user count you see in your [Metabase Store account page](https://store.metabase.com) every day. Since the refresh only happens once a day, there might be a delay between when you adjust the number of user accounts in your Metabase and when your accounts sync with your Store page.diff --git a/docs/cloud/migrate/cloud-to-self-hosted.md b/docs/cloud/migrate/cloud-to-self-hosted.mdindex 115b46381c8..957eab6fcf6 100644--- a/docs/cloud/migrate/cloud-to-self-hosted.md+++ b/docs/cloud/migrate/cloud-to-self-hosted.md@@ -48,7 +48,7 @@ If you're migrating from a Metabase Cloud Pro plan to a self-hosted Pro plan, yo2. **Download the snapshot from Metabase Store**. The email from Metabase Success Engineering will have a link to your download. You'll need to log in to the Metabase Store to access the download.- The snapshot of your Metabase Cloud application database will be an H2 file database: a file with the extension `.mv.db`. (Metabase Cloud instances use PostgresSQL for application databases, but snapshots are saved in H2 format, so that you can restore to either PostgresSQL or MysQL application databases).+ The snapshot of your Metabase Cloud application database will be an H2 file database: a file with the extension `.mv.db`. (Metabase Cloud instances use PostgreSQL for application databases, but snapshots are saved in H2 format, so that you can restore to either PostgreSQL or MysQL application databases).Snapshots expire quickly, but don't sweat it; if your snapshot has expired, just request a new one.diff --git a/docs/configuring-metabase/environment-variables.md b/docs/configuring-metabase/environment-variables.mdindex 8f45482b008..ba78c6fedf2 100644--- a/docs/configuring-metabase/environment-variables.md+++ b/docs/configuring-metabase/environment-variables.md@@ -1599,7 +1599,7 @@ Used for encrypting and checking whether SDK requests are signed.- Default: `null`When using the appdb engine against postgresql, override the language used for stemming in to_tsvector.- Value must be a valid configured langauge option in your database such as 'english' or 'simple'.+ Value must be a valid configured language option in your database such as 'english' or 'simple'.### `MB_SEARCH_TYPEAHEAD_ENABLED`diff --git a/docs/configuring-metabase/localization.md b/docs/configuring-metabase/localization.mdindex b4d75d27a49..f1c7197688b 100644--- a/docs/configuring-metabase/localization.md+++ b/docs/configuring-metabase/localization.md@@ -139,4 +139,4 @@ This setting doesn't affect [SQL queries](../questions/native-editor/writing-sql## Localizing embedded Metabase-You can tranlate both Metabase UI elements (like button labels) and content (like dashboard names) in static embeds. See [Setting the language for static embeds](../embedding/static-embedding-parameters.md#setting-the-language-for-a-static-embed) and [Translating embedded dashboards and questions](../embedding/translations.md).+You can translate both Metabase UI elements (like button labels) and content (like dashboard names) in static embeds. See [Setting the language for static embeds](../embedding/static-embedding-parameters.md#setting-the-language-for-a-static-embed) and [Translating embedded dashboards and questions](../embedding/translations.md).diff --git a/docs/data-modeling/json-unfolding.md b/docs/data-modeling/json-unfolding.mdindex aadd2756bfb..21bc67c61be 100644--- a/docs/data-modeling/json-unfolding.md+++ b/docs/data-modeling/json-unfolding.md@@ -55,7 +55,7 @@ If performance degrades, or you'd rather keep the JSON contained in the original4. Select the database that contains the field you want to update.5. Select the table that contains the field.6. Select the field containing the original JSON-7. In the **Behavior** section, locate the **Unfold JSON** option and select **Yes** or **No**. If the column was unfolded, Metabase will have hidden this JSON columnn from view, so if you want the JSON column to be visible again, you'll need to change the column's visibility to **Everywhere**.+7. In the **Behavior** section, locate the **Unfold JSON** option and select **Yes** or **No**. If the column was unfolded, Metabase will have hidden this JSON column from view, so if you want the JSON column to be visible again, you'll need to change the column's visibility to **Everywhere**.8. Scroll to the top and click the **Filter values** button and select **Re-scan this field**.diff --git a/docs/databases/ssl-certificates.md b/docs/databases/ssl-certificates.mdindex 25bc41db204..ad393e067a9 100644--- a/docs/databases/ssl-certificates.md+++ b/docs/databases/ssl-certificates.md@@ -65,7 +65,7 @@ You'll add an ampersand (`&`) to separate each parameter. For example, In the **sslmode=verify-full&sslrootcert=/path/to/certificate.pem```-Replace `/path/to/certifcate.pem` with the full path for the certificate you downloaded from your provider.+Replace `/path/to/certificate.pem` with the full path for the certificate you downloaded from your provider.You can learn more about [SSL support for PostgreSQL](https://www.postgresql.org/docs/current/libpq-ssl.html).diff --git a/docs/databases/users-roles-privileges.md b/docs/databases/users-roles-privileges.mdindex e1236438d01..2bb8d6f6c62 100644--- a/docs/databases/users-roles-privileges.md+++ b/docs/databases/users-roles-privileges.md@@ -63,7 +63,7 @@ GRANT analytics TO metabase;-- GRANT SELECT ON "your_table" IN SCHEMA "your_schema" TO analytics;```-Depending on how you use Metabase, you can also additonally grant:+Depending on how you use Metabase, you can also additionally grant:- `TEMPORARY` privileges to create temp tables.- `EXECUTE` privileges to use stored procedures or user-defined functions.diff --git a/docs/developers-guide/api-changelog.md b/docs/developers-guide/api-changelog.mdindex e50998f80f0..0a416427438 100644--- a/docs/developers-guide/api-changelog.md+++ b/docs/developers-guide/api-changelog.md@@ -79,7 +79,7 @@ title: API changelog- `POST /api/user/:id/send_invite` has been removed.- `GET /:id/fields` now includes the Table ID.-- APIs under `/api/pulse` and `/api/alert` will be removed in a future version as we're tranitioning to a new architecture.+- APIs under `/api/pulse` and `/api/alert` will be removed in a future version as we're transitioning to a new architecture.## Metabase 0.51.0diff --git a/docs/developers-guide/devenv.md b/docs/developers-guide/devenv.mdindex f0652e56b72..39f10f23a65 100644--- a/docs/developers-guide/devenv.md+++ b/docs/developers-guide/devenv.md@@ -176,7 +176,7 @@ several properties that can be set as environment variables or in a `deps.edn`."-Dmb.db.pass="]}}}```-You could also pass a full conection string in as the `mb.db.connection.uri`:+You could also pass a full connection string in as the `mb.db.connection.uri`:```"-Dmb.db.connection.uri=postgres://<user>:<password>@localhost:5432/<dbname>"diff --git a/docs/developers-guide/driver-changelog.md b/docs/developers-guide/driver-changelog.mdindex b9b82caedd1..2778ad2c23e 100644--- a/docs/developers-guide/driver-changelog.md+++ b/docs/developers-guide/driver-changelog.md@@ -157,13 +157,13 @@ title: Driver interface changelog## Metabase 0.54.11-- The multimethods `metabase.driver.sql-jdbc.sync.interface/active-tables` and `metabase.driver.sql-jdbc.sync.interface/filtered-syncable-schemas`, aswell as the functions+- The multimethods `metabase.driver.sql-jdbc.sync.interface/active-tables` and `metabase.driver.sql-jdbc.sync.interface/filtered-syncable-schemas`, as well as the functions`metabase.driver.sql-jdbc.sync.describe_database/fast-active-tables`, `metabase.driver.sql-jdbc.sync.describe_database/have-select-privilege-fn` and `metabase.driver.sql-jdbc.sync.describe_database/db-tables` now take a database spec instead of a `java.sql.Connection` object.## Metabase 0.54.10- Add `metabase.driver/table-known-to-not-exist?` for drivers to test if an exception is due to a query on a table that no longer exists-- Add `metabase.driver.sql-jdbc/impl-table-known-to-not-exist?` for JDBC drivers. This is the implemenation of table-known-to-not-exist for jdbc and allows testing directly against `java.sql.SQLException` throwables without worrying about the exception cause chain.+- Add `metabase.driver.sql-jdbc/impl-table-known-to-not-exist?` for JDBC drivers. This is the implementation of table-known-to-not-exist for jdbc and allows testing directly against `java.sql.SQLException` throwables without worrying about the exception cause chain.## Metabase 0.54.0@@ -195,7 +195,7 @@ title: Driver interface changelog## Metabase 0.53.12- Add `metabase.driver/query-canceled?` for drivers to test if an exception is due to a query being canceled due to user action-- Add `metabase.driver.sql-jdbc/impl-query-canceled?` for JDBC drivers. This is the implemenation of query-canceled for jdbc and allows testing directly against `java.sql.SQLException` throwables without worrying about the exception cause chain.+- Add `metabase.driver.sql-jdbc/impl-query-canceled?` for JDBC drivers. This is the implementation of query-canceled for jdbc and allows testing directly against `java.sql.SQLException` throwables without worrying about the exception cause chain.## Metabase 0.53.10@@ -641,7 +641,7 @@ title: Driver interface changelogto be assigned to specific database roles which are set before any queries are executed, so that access to tables canbe restricted at the database level instead of (or in conjunction with) Metabase's built-in permissions system.-- The multimethod `metabase.driver.sql-jdbc.sync.describe-table/get-table-pks` is changed to return a vector instea+- The multimethod `metabase.driver.sql-jdbc.sync.describe-table/get-table-pks` is changed to return a vector insteadof a set.- The function `metabase.query-processor.timezone/report-timezone-id-if-supported` has been updated to take an additional@@ -839,8 +839,8 @@ differences between the library versions.**Note: we expect these breaking changes to be fixed before 0.46.0 ships. This will be updated if they are.**-The classes `metabase.util.honeysql_extensions.Identifer` and `metabase.util.honeysql_extensions.TypedHoneySQLForm`-have been moved to `metabase.util.honey_sql_1.Identifer` and `metabase.util.honey_sql_1.TypedHoneySQLForm`,+The classes `metabase.util.honeysql_extensions.Identifier` and `metabase.util.honeysql_extensions.TypedHoneySQLForm`+have been moved to `metabase.util.honey_sql_1.Identifier` and `metabase.util.honey_sql_1.TypedHoneySQLForm`,respectively. On the off chance that your driver directly referencing these class names, you may need to update thingsto use the new class names.diff --git a/docs/developers-guide/drivers/driver-tests.md b/docs/developers-guide/drivers/driver-tests.mdindex 4af9a838aed..21ddb9e4c80 100644--- a/docs/developers-guide/drivers/driver-tests.md+++ b/docs/developers-guide/drivers/driver-tests.md@@ -174,7 +174,7 @@ You'll almost certainly be running your database in a local Docker container. RaTells Metabase to look for the environment variable `MB_MYSQL_TEST_USER`; if not found, default to `"root"`. The name of the environment variable follows the pattern `MB_<driver>_TEST_<property>`, as passed into the function as first and second args, respectively. You don't need to specify a default value for `tx/db-test-env-var`; perhaps `user` is an optional parameter; and if `MB_MYSQL_TEST_USER` isn't specified, you don't need to specify it in the connection details.-But what about properties you want to require, but do not have sane defaults? In those cases, you can use `tx/db-test-env-var-or-throw`. It the corresponding enviornment variable isn't set, these will throw an Exception, ultimately causing tests to fail.+But what about properties you want to require, but do not have sane defaults? In those cases, you can use `tx/db-test-env-var-or-throw`. It the corresponding environment variable isn't set, these will throw an Exception, ultimately causing tests to fail.```clj;; If MB_SQLSERVER_TEST_USER is unset, the test suite will quit with a message saying something like@@ -190,7 +190,7 @@ Besides `tx/db-test-env-var`, `metabase.test.data.interface` has several other hThere's a few other things Metabase needs to know when comparing test results. For example, different databases name tables and columns in different ways; methods exist to let Metabase know it should expect something like the `venues` table in the `test-data` Database Definition to come back as `VENUES` for a database that uppercases everything. (We consider such minor variations in naming to still mean the same thing.) Take a look at `tx/format-name` and other methods like that and see which ones you need to implement.-## What about DBMSes that don't let you create new databases programatically?+## What about DBMSes that don't let you create new databases programmatically?This is actually a common problem, and luckily we have figured out how to work around it. The solution is usually something like using different _schemas_ in place of different databases, or prefixing table names with the database name, and creating everything in the same database. For SQL-based databases, you can implement `sql.tx/qualified-name-components` to have tests use a different identifier instead of what they would normally use, for example `"shared_db"."test-data_venues".id` instead of `"test-data".venues.id`. The SQL Server and Oracle test extensions are good examples of such black magic in action.diff --git a/docs/developers-guide/drivers/plugins.md b/docs/developers-guide/drivers/plugins.mdindex f953c082c05..7aab50fbca5 100644--- a/docs/developers-guide/drivers/plugins.md+++ b/docs/developers-guide/drivers/plugins.md@@ -159,7 +159,7 @@ driver:# Whether loading this driver can be deferred until the first# attempt to connect to a database of this type. Default: true. Only- # set this to false if absolutely neccesary.+ # set this to false if absolutely necessary.lazy-load: true# Parent driver, if any.diff --git a/docs/developers-guide/e2e-tests.md b/docs/developers-guide/e2e-tests.mdindex 151b3096f53..8e9815624b0 100644--- a/docs/developers-guide/e2e-tests.md+++ b/docs/developers-guide/e2e-tests.md@@ -4,7 +4,7 @@ title: End-to-end tests with Cypress# End-to-end tests with Cypress-Metabase uses Cypress for “end-to-end testing”, that is, tests that are executed against the application as a whole, including the frontend, backend, and application database. These tests are essentially scripts written in JavaScript that run in the web browser: visit different URLs, click various UI elements, type text, and assert that things happen as expected (for example, an element appearing on screen, or a network request occuring).+Metabase uses Cypress for “end-to-end testing”, that is, tests that are executed against the application as a whole, including the frontend, backend, and application database. These tests are essentially scripts written in JavaScript that run in the web browser: visit different URLs, click various UI elements, type text, and assert that things happen as expected (for example, an element appearing on screen, or a network request occurring)._Please, get familiar with the [Cypress best practices](https://docs.cypress.io/app/core-concepts/best-practices) before you proceed._diff --git a/docs/embedding/sdk/dashboards.md b/docs/embedding/sdk/dashboards.mdindex 3f3c33d417d..d9d3b61fdfe 100644--- a/docs/embedding/sdk/dashboards.md+++ b/docs/embedding/sdk/dashboards.md@@ -160,7 +160,7 @@ Until the Embedded analytics SDK is fully loaded and initialized, the hook retur### `CreateDashboardModal`-#### API Refernce+#### API Reference- [Component](./api/CreateDashboardModal.html)- [Props](./api/CreateDashboardModalProps.html)diff --git a/docs/installation-and-operation/creating-RDS-database-on-AWS.md b/docs/installation-and-operation/creating-RDS-database-on-AWS.mdindex d48620b387a..27caecd6347 100644--- a/docs/installation-and-operation/creating-RDS-database-on-AWS.md+++ b/docs/installation-and-operation/creating-RDS-database-on-AWS.md@@ -51,7 +51,7 @@ Once the database status is `Available`, you need to click on the DB identifier:-On the page that appears after you click on the database identifer, you will see on the center of the page the **Connectivity & Security** section. This section will provide you with the **Endpoint** that Metabase needs to connect to the application database we just created.+On the page that appears after you click on the database identifier, you will see on the center of the page the **Connectivity & Security** section. This section will provide you with the **Endpoint** that Metabase needs to connect to the application database we just created.diff --git a/docs/installation-and-operation/development-instance.md b/docs/installation-and-operation/development-instance.mdindex 5d80edf3d92..a23a88b5e9b 100644--- a/docs/installation-and-operation/development-instance.md+++ b/docs/installation-and-operation/development-instance.md@@ -11,7 +11,7 @@ summary: Create development instances of Metabase for testing without paying perOn Pro and Enterprise plans, you can purchase a development instance or development token as an add-on to your plan.-- **Self-hosted**: you can purchase a dev token so you don't get billed for every test user acccount. You can use the same dev token for one or more self-hosted development instances (meaning: you can reuse the same token for multiple dev instances at no additional cost). The development token will have access to the same set of paid features as your production token.+- **Self-hosted**: you can purchase a dev token so you don't get billed for every test user account. You can use the same dev token for one or more self-hosted development instances (meaning: you can reuse the same token for multiple dev instances at no additional cost). The development token will have access to the same set of paid features as your production token.- **Cloud**: you can purchase a development instance hosted on [Metabase Cloud](https://www.metabase.com/cloud/). The development instance will have access to the same set of paid features as your production token.Dev instances are only available to Pro and Enterprise plans; they're not included in the base plans. Dev instances must be purchased as an add-on to your plan, after you've completed your trial and made your first payment.diff --git a/docs/installation-and-operation/upgrading-metabase.md b/docs/installation-and-operation/upgrading-metabase.mdindex eec75bb79ae..59f9623e6b3 100644--- a/docs/installation-and-operation/upgrading-metabase.md+++ b/docs/installation-and-operation/upgrading-metabase.md@@ -136,7 +136,7 @@ Metabase will do all this automatically.If you need to downgrade after a major version upgrade, you'll either need to restore from a backup, or manually migrate to a lower version, otherwise Metabase may refuse to start (see the next section).-Durning a **minor version upgrade** (e.g., 54.1 to 54.2), the new Metabase container or Jar will just work. Only in rare cases will it have to perform a migration, but, like with major version upgrades, Metabase will perform the migration automatically. And of course, you're backing up your application database each time you upgrade, right?+During a **minor version upgrade** (e.g., 54.1 to 54.2), the new Metabase container or Jar will just work. Only in rare cases will it have to perform a migration, but, like with major version upgrades, Metabase will perform the migration automatically. And of course, you're backing up your application database each time you upgrade, right?## Rolling back an upgrade or to an older version@@ -181,7 +181,7 @@ Once the migration process completes, start up Metabase using the JAR or containIf you're running Metabase in a cluster:-1. Reduce the number of nodes to a single node. You can't upgrade all nodes at the same time because the ugprade process works by acquiring a migration lock on the application database from a single client, which performs the migration. If you keep more than one node active when you do a major version upgrade, the application won't behave correctly, as schema changes to the application database could cause problems for nodes that are still running the older version of Metabase.+1. Reduce the number of nodes to a single node. You can't upgrade all nodes at the same time because the upgrade process works by acquiring a migration lock on the application database from a single client, which performs the migration. If you keep more than one node active when you do a major version upgrade, the application won't behave correctly, as schema changes to the application database could cause problems for nodes that are still running the older version of Metabase.2. Perform the upgrade as normal (as outlined above).3. Raise the number of nodes to the same number you had before.diff --git a/docs/permissions/impersonation.md b/docs/permissions/impersonation.mdindex 35305b38e56..b609e353c64 100644--- a/docs/permissions/impersonation.md+++ b/docs/permissions/impersonation.md@@ -15,7 +15,7 @@ This page covers the [View data](./data.md#view-data-permissions) permission levFor now, impersonation access is only available for the following databases:- ClickHouse- MySQL-- PostgreSQL. If you're using views in PostgresSQL, the row-level security policies on views will only work on Postgres versions 15 and higher.+- PostgreSQL. If you're using views in PostgreSQL, the row-level security policies on views will only work on Postgres versions 15 and higher.- Redshift- Snowflake- SQL Server@@ -179,6 +179,6 @@ Blue group's more permissive access would override the impersonated access.Admins won't ever see the effects of impersonation effects, because their privileges will override those of any other group they're a member of.-Metabase's default Administrators group has "Can view" access to all databases, and Metabase uses the most permissive access for any person in multple groups, so any admin will have "Can view" - not "Impersonated" - access to the database.+Metabase's default Administrators group has "Can view" access to all databases, and Metabase uses the most permissive access for any person in multiple groups, so any admin will have "Can view" - not "Impersonated" - access to the database.To test impersonation, create a test user, assign them a user attribute with the database role, and add them to the impersonated group. Then, log in as the test user and verify the data access.diff --git a/docs/permissions/row-and-column-security-examples.md b/docs/permissions/row-and-column-security-examples.mdindex acb85bb2599..9357de3bb2c 100644--- a/docs/permissions/row-and-column-security-examples.md+++ b/docs/permissions/row-and-column-security-examples.md@@ -95,7 +95,7 @@ Here are the results:We'll call this question "Filtered people table". Save it to the "Admins collection" you created in the setup (or any collection that only Admins have access to).-2. **Use a SQL question to create a custom view for this table**: We'll go to the Permissions section and grant this group row and column secuity to this table. This time we'll select the second option, "Use a saved question to create a custom view for this table", and select the question we just created ("Filtered people table"), like so:+2. **Use a SQL question to create a custom view for this table**: We'll go to the Permissions section and grant this group row and column security to this table. This time we'll select the second option, "Use a saved question to create a custom view for this table", and select the question we just created ("Filtered people table"), like so:diff --git a/docs/permissions/row-and-column-security.md b/docs/permissions/row-and-column-security.mdindex 31361fde7dc..6f4aaebde57 100644--- a/docs/permissions/row-and-column-security.md+++ b/docs/permissions/row-and-column-security.md@@ -274,7 +274,7 @@ To prevent the Email column from being exposed via a SQL question:### Public sharing-Row and column security permissions don't apply to public questions or public dashboards. If somone in an unsecured group creates a public link using an original table, the original table will be displayed to anyone who has the public link URL.+Row and column security permissions don't apply to public questions or public dashboards. If someone in an unsecured group creates a public link using an original table, the original table will be displayed to anyone who has the public link URL.To prevent this from happening, you'll have to [disable public sharing](../embedding/public-links.md) for your Metabase.diff --git a/docs/questions/alerts.md b/docs/questions/alerts.mdindex b88cb8417d8..0d0bd0e742b 100644--- a/docs/questions/alerts.md+++ b/docs/questions/alerts.md@@ -81,7 +81,7 @@ To create an alert when a time series crosses a goal line:- Whether you want Metabase to alert you every time the time series crosses a goal line, or only the first time it crosses the goal line.- How often you want Metabase to check to see if the goal line has been crossed.-7. Select the schedule and recepients for the alert, and click "Done"+7. Select the schedule and recipients for the alert, and click "Done"## Progress bar alertsdiff --git a/docs/questions/visualizations/map.md b/docs/questions/visualizations/map.mdindex 0cce86c373b..8c054be13dd 100644--- a/docs/questions/visualizations/map.md+++ b/docs/questions/visualizations/map.md@@ -57,7 +57,7 @@ To change the pin type:- **Markers**. Maps display up to 1,000 markers. If you choose the marker pin type for results with more than 1,000 rows, Metabase will still only display 1,000 markers. Maps default to markers for results fewer then 1,000 rows.- **Tiles**. Maps display up to 2,000 tiles. Maps default to tiles for results greater than 1,000 rows. Tooltips will not be displayed for tiles.-By default, maps can't display more than 2,000 individual unaggregated data points, regardless of the pin type. This limit is the same for every chart displaying unaggregated data in Metabase. To increase the number of data points rendered on charts based on unaggregated queries, you can use the environment variable [`MB_UNAGGREGATED_QUERY_ROW_LIMIT`](../../configuring-metabase/environment-variables.md#mb_unaggregated_query_row_limit). This setting will affect data points on _all_ charts—not just the pin maps—so increasing the limit too much could significantly slow down your Metabase and your browswer.+By default, maps can't display more than 2,000 individual unaggregated data points, regardless of the pin type. This limit is the same for every chart displaying unaggregated data in Metabase. To increase the number of data points rendered on charts based on unaggregated queries, you can use the environment variable [`MB_UNAGGREGATED_QUERY_ROW_LIMIT`](../../configuring-metabase/environment-variables.md#mb_unaggregated_query_row_limit). This setting will affect data points on _all_ charts—not just the pin maps—so increasing the limit too much could significantly slow down your Metabase and your browser.If you need to display a large number of geographic data points, consider using a grid map to display the distribution instead.diff --git a/docs/troubleshooting-guide/ldap.md b/docs/troubleshooting-guide/ldap.mdindex 0f29299ec35..5dfcc035f06 100644--- a/docs/troubleshooting-guide/ldap.md+++ b/docs/troubleshooting-guide/ldap.md@@ -57,7 +57,7 @@ networks:driver: bridge```-If you don't pass environment variables to Metabase and you want to configure the environment manually, you can go to the Admin Panel, selectin "Settings", select "Authentication", and then select "LDAP Configuration" and enter the following values:+If you don't pass environment variables to Metabase and you want to configure the environment manually, you can go to the Admin Panel, select "Settings", select "Authentication", and then select "LDAP Configuration" and enter the following values:- `USERNAME OR DN`: `cn=admin,dc=example,dc=org`- `PASSWORD`: `adminpassword`diff --git a/docs/troubleshooting-guide/timezones.md b/docs/troubleshooting-guide/timezones.mdindex 6750681ab99..82846ccffee 100644--- a/docs/troubleshooting-guide/timezones.md+++ b/docs/troubleshooting-guide/timezones.md@@ -40,7 +40,7 @@ Once you think you have identified a problem, drill down to understand exactly w## Is the Report Time Zone set incorrectly?-**Root cause:** Wrong numbers in questions or charts can be caused by a mis-match in the time zone being used by Metabase and the time zone being used by the data warehouse.+**Root cause:** Wrong numbers in questions or charts can be caused by a mismatch in the time zone being used by Metabase and the time zone being used by the data warehouse.**Steps to take:**diff --git a/mage/src/mage/codespell.clj b/mage/src/mage/codespell.cljnew file mode 100644index 00000000000..c8b3df0a31f--- /dev/null+++ b/mage/src/mage/codespell.clj@@ -0,0 +1,57 @@+(ns mage.codespell+ (:require+ [mage.shell :as shell]+ [clojure.string :as str]))++(set! *warn-on-reflection* true)++(def ^:private codespell-dirs+ "Keep these in sync with the list of directories in `.github/workflows/codespell.yml`."+ [#_"dev"+ "docs"+ #_"e2e"+ #_"enterprise"+ #_"frontend"+ #_"modules/drivers"+ #_"src"+ #_"test"])++(defn codespell [_cli-args]+ (let [{:keys [exit], :or {exit -1}} (apply shell/sh*+ "codespell"+ codespell-dirs)]+ (System/exit exit)))++(defn codespell-interactive [_cli-args]+ (let [command (list*+ "codespell"+ ;; ask for confirmation, and allow user to choose fix when more than one+ ;; is available+ "--interactive" 3+ codespell-dirs)]+ (println "Interactive command support for MAGE doesn't seem to work yet, so please run this by doing")+ (println)+ (apply println command)+ (System/exit 0)))++;; evaluate this to regenerate the list in `.codespellrc`+(comment+ (def ^:private ignored-files+ "List of files/directories to exempt from CodeSpell linting."+ (str/join "," ["*.csv"+ "*.edn"+ "*.geojson"+ "*.json"+ "*.tsv"+ "*.xml"+ "docs/developers-guide/drivers/driver-tests.md"+ "docs/developers-guide/e2e-tests.md"+ "docs/questions/query-builder/expressions-list.md"+ "docs/questions/visualizations/country-codes.md"+ "e2e/test/scenarios/admin/i18n/content-translation/constants.ts"+ "frontend/src/cljs"+ "frontend/src/metabase/querying/expressions/tokenizer/lezer.js"+ "frontend/src/metabase/static-viz/constants/char-sizes.ts"+ "frontend/src/metabase/visualizations/lib/mapping_codes.ts"+ "modules/drivers/mongo/src/metabase/driver/mongo/operators.clj"+ ])))