[auto] adding content to albertoperdomo-sdk-docs-npm-link->master (#321)

Co-authored-by: Metabase Docs bot <[email protected]>

Author: github-automation-metabase

_docs/master/databases/connections/bigquery.md

@@ -168,6 +168,12 @@ If you're having trouble with your BigQuery connection, you can check out this [
 
 There aren't (yet) any model features available for BigQuery.
 
+## Database routing
+
+Database routing for BigQuery works between BigQuery **projects** with identical schemas.
+
+See [Database routing](../../permissions/database-routing).
+
 ## Danger zone
 
 See [Danger zone](../danger-zone).

_docs/master/databases/connections/mongodb.md

@@ -121,7 +121,7 @@ Learn more about [configuring SSL with MongoDB](http://mongodb.github.io/mongo-j
 
 ## How Metabase syncs data in MongoDB
 
-Because MongoDB contains unstructured data, Metabase takes a different approach to syncing your database's metadata. To get a sense of the schema, Metabase will query the first and last 500 documents (most of the calculation is done in MongoDB). This sampling helps Metabase do things like differentiate datetime fields from string fields, and provide people with pre-populated filters. The reason Metabase only scans a sample of the documents is because scanning every document in every collection on every sync would put too much strain on your database. And while the sampling does a pretty good job keeping Metabase up to date, it can also mean that new fields can sometimes fall through the cracks, leading to visualization issues, or even fields failing to appear in your results. For more info, check out our [troubleshooting guide](../../troubleshooting-guide/db-connection).
+Because MongoDB contains unstructured data, Metabase takes a different approach to syncing your database's metadata. To get a sense of the schema, Metabase will query the first and last 500 documents (most of the calculation is done in MongoDB). This sampling helps Metabase do things like differentiate datetime fields from string fields, and provide people with pre-populated filters. Metabase also syncs 1,000 leaf fields (fields at the deepest nesting level) per MongoDB collection. The reason Metabase only scans a sample of the documents is because scanning every document in every collection on every sync would put too much strain on your database. And while the sampling does a pretty good job keeping Metabase up to date, it can also mean that new fields can sometimes fall through the cracks, leading to visualization issues, or even fields failing to appear in your results. For more info, check out our [troubleshooting guide](../../troubleshooting-guide/db-connection).
 
 ## General connectivity concerns
 

_docs/master/developers-guide/driver-changelog.md

@@ -27,6 +27,9 @@ layout: new-docs
   replace existing keys like `:alias`, `:join-alias`, or `:name`; make sure you use `driver-api/qp.add.alias`,
   `driver-api/qp.add.source-table`, and `driver-api/qp.add.source-alias` respectively.
 
+- Added the driver multi-method `driver/extra-info` for drivers to provide info such as db routing configuration details
+  from their `metabase-plugin.yaml` file.
+
 - Extend `datetime()` to accept UTF-8 encoded binary and numbers (unix timestamps) in addition to strings.
 
 - Added a feature `:expressions/today` for drivers that support generating a date for the current day.
@@ -58,7 +61,6 @@ layout: new-docs
   `metabase.driver/upload-type->database-type` or `metabase.driver/allowed-promotions` -- make sure you use
   `:metabase.upload/varchar-255` rather than something like `::upload/varchar-255`.
 
-- Added the multi-method `metabase.driver.sql.parameters.substitution/time-grouping->replacement-snippet-info`.  This is effectively `->replacement-snippet-info` for the new native query time grouping feature, but is its own separate multimethod because it needs an extra parameter.
 - The `metabase.models.secret` namespace has been replaced with `metabase.secrets.core`; if you were using it please
   update your usages.
 

_docs/master/embedding/sdk/introduction.md

@@ -114,7 +114,7 @@ View the SDK's changelog:
 
 ## Embedded analytics SDK on NPM
 
-Check out the Metabase Embedded analytics SDK on NPM: [metaba.se/sdk](https://metaba.se/sdk).
+Check out the Metabase Embedded analytics SDK on NPM: [metaba.se/sdk-npm](https://metaba.se/sdk-npm).
 
 ## SDK limitations
 
@@ -125,7 +125,11 @@ The SDK doesn't support:
 - Subscriptions
 - Alerts
 - Server-side rendering (SSR)
+
+Other limitations:
+
 - Multiple _interactive_ dashboards on the same application page. If you need to embed multiple dashboards on the same application page, you can embed static dashboards.
+- If you have Leaflet 1.x as a dependency in your app, you may run into compatibility issues. You can try using Leaflet 2.x instead.
 
 ## Issues, feature requests and support
 

_docs/master/people-and-groups/saml-google.md

@@ -68,7 +68,9 @@ For example, to add the attribute "First name":
 
 ## Setting up synchronize group membership
 
-1. In Google Admin, setup a multi-value [custom user attribute](https://support.google.com/a/answer/6208725?hl=en#zippy=%2Cadd-a-new-custom-attribute) for your users (recommended if you manage multiple SAML app permissions in Google or do not have existing Google Groups that align with your desired Metabase groups) OR [map to existing Google Groups](https://support.google.com/a/answer/11143403?hl=en).
+1. In Google Admin, you can EITHER:
+     - Set up a multi-value [custom user attribute](https://support.google.com/a/answer/6208725?hl=en#zippy=%2Cadd-a-new-custom-attribute) for your users. Recommended if you manage multiple SAML app permissions in Google or if you lack existing Google Groups that align with your desired Metabase groups.
+     - [Map to existing Google Groups](https://support.google.com/a/answer/11143403?hl=en).
 2. Follow the instructions for [Configuring the group schema](./authenticating-with-saml#configuring-the-group-schema-in-metabase) using the `App attribute` that you used in Google as the Group attribute name in Metabase.
 
 ## Troubleshooting SAML issues

_docs/master/permissions/database-routing.md

@@ -25,6 +25,7 @@ Database routing is useful for:
 
 ## Databases that support database routing
 
+- [BigQuery](../databases/connections/bigquery)
 - [Druid](../databases/connections/druid)
 - [MongoDB](../databases/connections/mongodb)
 - [MariaDB](../databases/connections/mariadb)

_site/docs/master/databases/connections/bigquery.html

@@ -4875,6 +4875,12 @@ <h2 id="model-features">Model features</h2>
 
 <p>There aren’t (yet) any model features available for BigQuery.</p>
 
+<h2 id="database-routing">Database routing</h2>
+
+<p>Database routing for BigQuery works between BigQuery <strong>projects</strong> with identical schemas.</p>
+
+<p>See <a href="../../permissions/database-routing">Database routing</a>.</p>
+
 <h2 id="danger-zone">Danger zone</h2>
 
 <p>See <a href="../danger-zone">Danger zone</a>.</p>

_site/docs/master/databases/connections/mongodb.html

@@ -4825,7 +4825,7 @@ <h2 id="configuring-ssl-via-the-command-line">Configuring SSL via the command li
 
 <h2 id="how-metabase-syncs-data-in-mongodb">How Metabase syncs data in MongoDB</h2>
 
-<p>Because MongoDB contains unstructured data, Metabase takes a different approach to syncing your database’s metadata. To get a sense of the schema, Metabase will query the first and last 500 documents (most of the calculation is done in MongoDB). This sampling helps Metabase do things like differentiate datetime fields from string fields, and provide people with pre-populated filters. The reason Metabase only scans a sample of the documents is because scanning every document in every collection on every sync would put too much strain on your database. And while the sampling does a pretty good job keeping Metabase up to date, it can also mean that new fields can sometimes fall through the cracks, leading to visualization issues, or even fields failing to appear in your results. For more info, check out our <a href="../../troubleshooting-guide/db-connection">troubleshooting guide</a>.</p>
+<p>Because MongoDB contains unstructured data, Metabase takes a different approach to syncing your database’s metadata. To get a sense of the schema, Metabase will query the first and last 500 documents (most of the calculation is done in MongoDB). This sampling helps Metabase do things like differentiate datetime fields from string fields, and provide people with pre-populated filters. Metabase also syncs 1,000 leaf fields (fields at the deepest nesting level) per MongoDB collection. The reason Metabase only scans a sample of the documents is because scanning every document in every collection on every sync would put too much strain on your database. And while the sampling does a pretty good job keeping Metabase up to date, it can also mean that new fields can sometimes fall through the cracks, leading to visualization issues, or even fields failing to appear in your results. For more info, check out our <a href="../../troubleshooting-guide/db-connection">troubleshooting guide</a>.</p>
 
 <h2 id="general-connectivity-concerns">General connectivity concerns</h2>
 

_site/docs/master/developers-guide/driver-changelog.html

@@ -4716,6 +4716,10 @@ <h2 id="metabase-0560">Metabase 0.56.0</h2>
     <p>Also note that <code class="language-plaintext highlighter-rouge">driver-api/add-alias-info</code> only adds additional keys to field refs and join maps, and does not
 replace existing keys like <code class="language-plaintext highlighter-rouge">:alias</code>, <code class="language-plaintext highlighter-rouge">:join-alias</code>, or <code class="language-plaintext highlighter-rouge">:name</code>; make sure you use <code class="language-plaintext highlighter-rouge">driver-api/qp.add.alias</code>,
 <code class="language-plaintext highlighter-rouge">driver-api/qp.add.source-table</code>, and <code class="language-plaintext highlighter-rouge">driver-api/qp.add.source-alias</code> respectively.</p>
+  </li>
+  <li>
+    <p>Added the driver multi-method <code class="language-plaintext highlighter-rouge">driver/extra-info</code> for drivers to provide info such as db routing configuration details
+from their <code class="language-plaintext highlighter-rouge">metabase-plugin.yaml</code> file.</p>
   </li>
   <li>
     <p>Extend <code class="language-plaintext highlighter-rouge">datetime()</code> to accept UTF-8 encoded binary and numbers (unix timestamps) in addition to strings.</p>
@@ -4764,7 +4768,6 @@ <h2 id="metabase-0550">Metabase 0.55.0</h2>
 <code class="language-plaintext highlighter-rouge">metabase.driver/upload-type-&gt;database-type</code> or <code class="language-plaintext highlighter-rouge">metabase.driver/allowed-promotions</code> – make sure you use
 <code class="language-plaintext highlighter-rouge">:metabase.upload/varchar-255</code> rather than something like <code class="language-plaintext highlighter-rouge">::upload/varchar-255</code>.</p>
   </li>
-  <li>Added the multi-method <code class="language-plaintext highlighter-rouge">metabase.driver.sql.parameters.substitution/time-grouping-&gt;replacement-snippet-info</code>.  This is effectively <code class="language-plaintext highlighter-rouge">-&gt;replacement-snippet-info</code> for the new native query time grouping feature, but is its own separate multimethod because it needs an extra parameter.</li>
   <li>
     <p>The <code class="language-plaintext highlighter-rouge">metabase.models.secret</code> namespace has been replaced with <code class="language-plaintext highlighter-rouge">metabase.secrets.core</code>; if you were using it please
 update your usages.</p>
@@ -4801,9 +4804,11 @@ <h2 id="metabase-0550">Metabase 0.55.0</h2>
   <li>
     <p>The namespace <code class="language-plaintext highlighter-rouge">metabase.query-processor.context</code>, deprecated in 0.50.0, has been removed.</p>
   </li>
-  <li>All settings formerly in a <code class="language-plaintext highlighter-rouge">metabase.driver.*</code> namespace have been moved to <code class="language-plaintext highlighter-rouge">metabase.driver.settings</code>, and all
+  <li>
+    <p>All settings formerly in a <code class="language-plaintext highlighter-rouge">metabase.driver.*</code> namespace have been moved to <code class="language-plaintext highlighter-rouge">metabase.driver.settings</code>, and all
 settings formerly in a <code class="language-plaintext highlighter-rouge">metabase.query-processor.*</code> namespace have been moved to
-<code class="language-plaintext highlighter-rouge">metabase.query-processor.settings</code>.</li>
+<code class="language-plaintext highlighter-rouge">metabase.query-processor.settings</code>.</p>
+  </li>
 </ul>
 
 <h2 id="metabase-05412">Metabase 0.54.12</h2>

_site/docs/master/embedding/sdk/introduction.html

@@ -4819,7 +4819,7 @@ <h2 id="changelog">Changelog</h2>
 
 <h2 id="embedded-analytics-sdk-on-npm">Embedded analytics SDK on NPM</h2>
 
-<p>Check out the Metabase Embedded analytics SDK on NPM: <a href="https://metaba.se/sdk">metaba.se/sdk</a>.</p>
+<p>Check out the Metabase Embedded analytics SDK on NPM: <a href="https://metaba.se/sdk-npm">metaba.se/sdk-npm</a>.</p>
 
 <h2 id="sdk-limitations">SDK limitations</h2>
 
@@ -4831,7 +4831,13 @@ <h2 id="sdk-limitations">SDK limitations</h2>
   <li>Subscriptions</li>
   <li>Alerts</li>
   <li>Server-side rendering (SSR)</li>
+</ul>
+
+<p>Other limitations:</p>
+
+<ul>
   <li>Multiple <em>interactive</em> dashboards on the same application page. If you need to embed multiple dashboards on the same application page, you can embed static dashboards.</li>
+  <li>If you have Leaflet 1.x as a dependency in your app, you may run into compatibility issues. You can try using Leaflet 2.x instead.</li>
 </ul>
 
 <h2 id="issues-feature-requests-and-support">Issues, feature requests and support</h2>