payload 1.10.4 → 1.11.0

package/docs/cloud/projects.mdx

@@ -0,0 +1,110 @@
+---
+title: Cloud Projects
+label: Projects
+order: 40
+desc: Manage your Payload Cloud projects.
+keywords: cloud, payload cloud, projects, project, overview, database, file storage, build settings, environment variables, custom domains, email, developing locally
+---
+
+### Overview
+
+<Banner>
+  The overview tab shows your most recent deployment, along with build and
+  deploy logs. From here, you can see your live URL, deployment details like
+  timestamps and commit hash, as well as the status of your deployment. You can
+  also trigger a redeployment manually, which will rebuild your project using
+  the current configuration.
+</Banner>
+
+![Payload Cloud Overview Page](https://payloadcms.com/images/docs/cloud/overview-page.jpg)
+_A screenshot of the Overview page for a Cloud project._
+
+### Database
+
+Your Payload Cloud project comes with a MongoDB serverless Atlas DB instance or Dedicated Atlas cluster, depending on your plan. To interact with your cloud database, you will be provided with a MongoDB connection string. This can be found under the **Database** tab of your project.
+
+`mongodb+srv://your_connection_string`
+
+### File Storage
+
+Payload Cloud gives you S3 file storage backed by Cloudflare as a CDN, and this plugin extends Payload so that all of your media will be stored in S3 rather than locally.
+
+AWS Cognito is used for authentication to your S3 bucket. The [Payload Cloud Plugin](https://github.com/payloadcms/plugin-cloud) will automatically pick up these values. These values are only if you'd like to access your files directly, outside of Payload Cloud.
+
+### Build Settings
+
+You can update settings from your Project’s Settings tab. Changes to your build settings will trigger a redeployment of your project.
+
+### Environment Variables
+
+From the Environment Variables page of the Settings tab, you can add, update and delete variables for use in your project. Like build settings, these changes will trigger a redeployment of your project.
+
+<Banner>
+  Note: For security reasons, any variables you wish to provide to the Admin
+  panel must be prefixed with `PAYLOAD_PUBLIC_`.  Learn more
+  [here](https://payloadcms.com/docs/admin/webpack#admin-environment-vars).
+</Banner>
+### Custom Domains
+
+With Payload Cloud, you can add custom domain names to your project. To do so, first go to the Domains page of the Settings tab of your project. Here you can see your default domain. To add a new domain, type in the domain name you wish to use.
+
+<Banner>
+  Note: do not include protocol (http:// or https://) or any routes (/page).
+  Only include the the domain name and extension, and optionally a subdomain. -
+  your-domain.com - backend.your-domain.com
+</Banner>
+
+Once you click save, a DNS record will be generated for your domain name to point to your live project. Add this record into your DNS provider’s records, and once the records are resolving properly (this can take 1hr to 48hrs in some cases), your domain will now to point to your live project.
+
+You will also need to configure your Payload project to use your specified domain. in your `payload.config.ts` file, specify your serverURL with your domain:
+
+```ts
+export default buildConfig({
+  serverURL: "https://example.com",
+  // the rest of your config,
+});
+```
+
+### Email
+
+Powered by Resend, Payload Cloud comes with integrated email support out of the box. No configuration is needed, and you can use `payload.sendEmail()` to send email right from your Payload app. To learn more about sending email with Payload, checkout the [Email Configuration](https://payloadcms.com/docs/email/overview) overview.
+
+If you are on the Pro or Enterprise plan, you can add your own custom Email domain name. From the Email page of your project’s Settings page, add the domain you wish to use for email delivery. This will generate a set of DNS records. Add these records to your DNS provider and click verify to check that your records are resolving properly. Once verified, your emails will now be sent from your custom domain name.
+
+### Developing Locally
+
+To make changes to your project, you will need to clone the repository defined in your project settings to your local machine. In order to run your project locally, you will need configure your local environment first. Refer to your repository’s `README.md` file to see the steps needed for your specific template.
+
+From there, you are ready to make updates to your project. When you are ready to make your changes live, commit your changes to the branch you specified in your Project settings, and your application will automatically trigger a redeploy and build from your latest commit.
+
+### Cloud Plugin
+
+Projects generated from a template will come pre-configured with the official Cloud Plugin, but if you are using your own repository you will need to add this into your project. To do so, add the plugin to your Payload config:
+
+`yarn add @payloadcms/plugin-cloud`
+
+```js
+import { payloadCloud } from "@payloadcms/plugin-cloud";
+import { buildConfig } from "payload/config";
+
+export default buildConfig({
+  plugins: [payloadCloud()],
+  // rest of config
+});
+```
+
+<Banner type="warning">
+  **Note:** If your Payload config already has an email with transport, this
+  will take precedence over Payload Cloud's email service.
+</Banner>
+
+##### **Optional configuration**
+
+If you wish to opt-out of any Payload cloud features, the plugin also accepts options to do so.
+
+```js
+payloadCloud({
+  storage: false, // Disable file storage
+  email: false, // Disable email delivery
+});
+```

package/docs/cloud/teams.mdx

@@ -0,0 +1,35 @@
+---
+title: Cloud Teams
+label: Teams
+order: 30
+desc: Manage your Payload Cloud team and billing settings.
+keywords: team, teams, billing, subscription, payment, plan, plans, cloud, payload cloud
+---
+
+<Banner>
+  Within Payload Cloud, the team management feature offers you the ability to
+  manage your organization, team members, billing, and subscription settings.
+</Banner>
+
+![Payload Cloud Team Settings](https://payloadcms.com/images/docs/cloud/team-settings.jpg)
+_A screenshot of the Team Settings page._
+
+### Members
+
+Each team has members that can interact with your projects. You can invite multiple people to your team and each individual can belong to more than one team. You can delegate whether they have `owner` or `user` permissions. Owners are able to make admin-only changes, such as deleting projects, and editing billing information.
+
+### Adding Members
+
+To add a new member to your team, visit your Team’s Settings page, and click “Invite Teammate”. You can then add their email address, and assign their role. Press “Save” to send invitations, which will send an email to the invited team member where they can create a new account.
+
+### Billing
+
+Users can update billing settings and subscriptions for any teams where they are designated as an `owner`. To make updates to the team’s payment methods, visit the Billing page under the Team Settings tab. You can add new cards, delete cards, and set a payment method as a default. The default payment method will be used in the event that another payment method fails.
+
+### Subscriptions
+
+From the Subscriptions page, a team owner can see all current plans for their team. From here, you can see the price of each plan, if there is an active trial, and when you will be billed next.
+
+### Invoices
+
+The Invoices page will you show you the invoices for your account, as well as the status on their payment.

package/docs/configuration/i18n.mdx

@@ -11,44 +11,49 @@ Not only does Payload support managing localized content, it also has internatio
 While Payload's built-in features come translated, you may want to also translate parts of your project's configuration too. This is possible in places like collections and globals labels and groups, field labels, descriptions and input placeholder text. The admin UI will display all the correct translations you provide based on the user's language.
 
 Here is an example of a simple collection supporting both English and Spanish editors:
+
 ```ts
-import { CollectionConfig } from 'payload/types';
+import { CollectionConfig } from "payload/types";
 
 export const Articles: CollectionConfig = {
-  slug: 'articles',
+  slug: "articles",
   labels: {
     singular: {
-      en: 'Article', es: 'Artículo',
+      en: "Article",
+      es: "Artículo",
     },
     plural: {
-      en: 'Articles', es: 'Artículos',
+      en: "Articles",
+      es: "Artículos",
     },
   },
   admin: {
-    group: { en: 'Content', es: 'Contenido' },
+    group: { en: "Content", es: "Contenido" },
   },
   fields: [
     {
-      name: 'title',
-      type: 'text',
+      name: "title",
+      type: "text",
       label: {
-        en: 'Title', es: 'Título',
+        en: "Title",
+        es: "Título",
       },
       admin: {
-        placeholder: { en: 'Enter title', es: 'Introduce el título' }
-      }
+        placeholder: { en: "Enter title", es: "Introduce el título" },
+      },
     },
     {
-      name: 'type',
-      type: 'radio',
-      options: [{
-        value: 'news',
-        label: { en: 'News', es: 'Noticias' },
-      }, // etc...
+      name: "type",
+      type: "radio",
+      options: [
+        {
+          value: "news",
+          label: { en: "News", es: "Noticias" },
+        }, // etc...
       ],
     },
   ],
-}
+};
 ```
 
 ### Admin UI
@@ -57,8 +62,8 @@ The Payload admin panel reads the language settings of a user's browser and disp
 After a user logs in, they can change their language selection in the `/account` view.
 
 <Banner>
-  <strong>Note:</strong><br/>
-  If there is a language that Payload does not yet support, we accept code <a href="https://github.com/payloadcms/payload/blob/master/contributing.md">contributions</a>.
+  <strong>Note:</strong><br />
+  If there is a language that Payload does not yet support, we accept code [contributions](https://github.com/payloadcms/payload/blob/master/contributing.md).
 </Banner>
 
 ### Node Express
@@ -76,21 +81,22 @@ In your Payload config, you can add translations and customize the settings in `
 **Example Payload config extending i18n:**
 
 ```ts
-import { buildConfig } from 'payload/config'
+import { buildConfig } from "payload/config";
 
 export default buildConfig({
   //...
   i18n: {
-    fallbackLng: 'en', // default
+    fallbackLng: "en", // default
     debug: false, // default
     resources: {
       en: {
-        custom: { // namespace can be anything you want
-          key1: 'Translation with {{variable}}', // translation
+        custom: {
+          // namespace can be anything you want
+          key1: "Translation with {{variable}}", // translation
         },
         // override existing translation keys
         general: {
-          dashboard: 'Home',
+          dashboard: "Home",
         },
       },
     },

package/docs/configuration/overview.mdx

@@ -122,9 +122,8 @@ project-name
   <br />
   If you use an environment variable to configure any properties that are
   required for the Admin panel to function (ex. serverURL or any routes), you
-  need to make sure that your Admin panel code can access it.{" "}
-  <a href="/docs/admin/webpack#admin-environment-vars">Click here</a> for more
-  info.
+  need to make sure that your Admin panel code can access it. [Click
+  here](/docs/admin/webpack#admin-environment-vars) for more info.
 </Banner>
 
 ### Customizing & overriding the config location

package/docs/email/overview.mdx

@@ -25,21 +25,22 @@ in the `email` property object of your payload init call. Payload will make use
 
 The following options are configurable in the `email` property object as part of the options object when calling payload.init().
 
-| Option                       | Description  |
-| ---------------------------- | -------------|
-| **`fromName`** *             | The name part of the From field that will be seen on the delivered email |
-| **`fromAddress`** *          | The email address part of the From field that will be used when delivering email |
-| **`transport`**              | The NodeMailer transport object for when you want to do it yourself, not needed when transportOptions is set |
-| **`transportOptions`**       | An object that configures the transporter that Payload will create. For all the available options see the [NodeMailer documentation](https://nodemailer.com/smtp/) or see the examples below |
-| **`logMockCredentials`**          | If set to true and no transport/transportOptions, ethereal credentials will be logged to console on startup |
+| Option                   | Description                                                                                                                                                                                  |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`fromName`** \*        | The name part of the From field that will be seen on the delivered email                                                                                                                     |
+| **`fromAddress`** \*     | The email address part of the From field that will be used when delivering email                                                                                                             |
+| **`transport`**          | The NodeMailer transport object for when you want to do it yourself, not needed when transportOptions is set                                                                                 |
+| **`transportOptions`**   | An object that configures the transporter that Payload will create. For all the available options see the [NodeMailer documentation](https://nodemailer.com/smtp/) or see the examples below |
+| **`logMockCredentials`** | If set to true and no transport/transportOptions, ethereal credentials will be logged to console on startup                                                                                  |
 
-*\* An asterisk denotes that a property is required.*
+_\* An asterisk denotes that a property is required._
 
 ### Use SMTP
 
 Simple Mail Transfer Protocol, also known as SMTP can be passed in using the `transportOptions` object on the `email` options.
 
 **Example email part using SMTP:**
+
 ```ts
 payload.init({
   email: {
@@ -47,24 +48,24 @@ payload.init({
       host: process.env.SMTP_HOST,
       auth: {
         user: process.env.SMTP_USER,
-        pass: process.env.SMTP_PASS
+        pass: process.env.SMTP_PASS,
       },
       port: 587,
       secure: true, // use TLS
       tls: {
         // do not fail on invalid certs
-        rejectUnauthorized: false
-        }
+        rejectUnauthorized: false,
       },
-    fromName: 'hello',
-    fromAddress: 'hello@example.com'
-  }
+    },
+    fromName: "hello",
+    fromAddress: "hello@example.com",
+  },
   // ...
-})
+});
 ```
 
 <Banner type="warning">
-  It is best practice to avoid saving credentials or API keys directly in your code, use <a href="/docs/configuration/overview#using-environment-variables-in-your-config">environment variables</a>.
+  It is best practice to avoid saving credentials or API keys directly in your code, use [environment variables](/docs/configuration/overview#using-environment-variables-in-your-config).
 </Banner>
 
 ### Use an email service
@@ -72,57 +73,62 @@ payload.init({
 Many third party mail providers are available and offer benefits beyond basic SMTP. As an example your payload init could look this if you wanted to use SendGrid.com though the same approach would work for any other [NodeMailer transports](https://nodemailer.com/transports/) shown here or provided by another third party.
 
 ```ts
-import payload from 'payload'
-import nodemailerSendgrid from 'nodemailer-sendgrid'
+import payload from "payload";
+import nodemailerSendgrid from "nodemailer-sendgrid";
 
 const sendGridAPIKey = process.env.SENDGRID_API_KEY;
 
 payload.init({
-  ...sendGridAPIKey ? {
-    email: {
-      transportOptions: nodemailerSendgrid({
-        apiKey: sendGridAPIKey,
-      }),
-      fromName: 'Admin',
-      fromAddress: 'admin@example.com',
-    },
-  } : {},
+  ...(sendGridAPIKey
+    ? {
+        email: {
+          transportOptions: nodemailerSendgrid({
+            apiKey: sendGridAPIKey,
+          }),
+          fromName: "Admin",
+          fromAddress: "admin@example.com",
+        },
+      }
+    : {}),
 });
 ```
 
 ### Use a custom NodeMailer transport
+
 To take full control of the mail transport you may wish to use `nodemailer.createTransport()` on your server and provide it to Payload init.
 
 ```ts
-import payload from 'payload'
-import nodemailer from 'nodemailer'
+import payload from "payload";
+import nodemailer from "nodemailer";
 
-const payload = require('payload');
-const nodemailer = require('nodemailer');
+const payload = require("payload");
+const nodemailer = require("nodemailer");
 
 const transport = await nodemailer.createTransport({
   host: process.env.SMTP_HOST,
   port: 587,
   auth: {
     user: process.env.SMTP_USER,
-    pass: process.env.SMTP_PASS
+    pass: process.env.SMTP_PASS,
   },
 });
 
 payload.init({
   email: {
-    fromName: 'Admin',
-    fromAddress: 'admin@example.com',
-    transport
+    fromName: "Admin",
+    fromAddress: "admin@example.com",
+    transport,
   },
   // ...
 });
 ```
 
 ### Sending Mail
+
 With a working transport you can call it anywhere you have access to payload by calling `payload.sendEmail(message)`. The `message` will contain the `to`, `subject` and `email` or `text` for the email being sent. To see all available message configuration options see [NodeMailer](https://nodemailer.com/message).
 
 ### Mock transport
+
 By default, Payload uses a mock implementation that only sends mail to the [ethereal](https://ethereal.email) capture service that will never reach a user's inbox. While in development you may wish to make use of the captured messages which is why the payload output during server output helpfully logs this out on the server console.
 
 To see ethereal credentials, add `logMockCredentials: true` to the email options. This will cause them to be logged to console on startup.
@@ -130,8 +136,8 @@ To see ethereal credentials, add `logMockCredentials: true` to the email options
 ```ts
 payload.init({
   email: {
-    fromName: 'Admin',
-    fromAddress: 'admin@example.com',
+    fromName: "Admin",
+    fromAddress: "admin@example.com",
     logMockCredentials: true, // Optional
   },
   // ...
@@ -139,6 +145,7 @@ payload.init({
 ```
 
 **Console output when starting payload with a mock email instance and logMockCredentials: true**
+
 ```
 [06:37:21] INFO  (payload): Starting Payload...
 [06:37:22] INFO  (payload): Payload Demo Initialized

package/docs/fields/relationship.mdx

@@ -25,8 +25,8 @@ keywords: relationship, fields, config, configuration, documentation, Content Ma
 | **`relationTo`** \* | Provide one or many collection `slug`s to be able to assign relationships to.                                                                                                                       |
 | **`filterOptions`** | A query to filter which options appear in the UI and validate against. [More](#filtering-relationship-options).                                                                                     |
 | **`hasMany`**       | Boolean when, if set to `true`, allows this field to have many relations instead of only one.                                                                                                       |
-| **`minRows`**           | A number for the fewest allowed items during validation when a value is present. Used with `hasMany`.                                                                                               |
-| **`maxRows`**           | A number for the most allowed items during validation when a value is present. Used with `hasMany`.                                                                                                 |
+| **`minRows`**       | A number for the fewest allowed items during validation when a value is present. Used with `hasMany`.                                                                                               |
+| **`maxRows`**       | A number for the most allowed items during validation when a value is present. Used with `hasMany`.                                                                                                 |
 | **`maxDepth`**      | Sets a number limit on iterations of related documents to populate when queried. [Depth](/docs/getting-started/concepts#depth)                                                                      |
 | **`label`**         | Text used as a field label in the Admin panel or an object with keys for each language.                                                                                                             |
 | **`unique`**        | Enforce that each entry in the Collection has a unique value for this field.                                                                                                                        |
@@ -47,8 +47,8 @@ _\* An asterisk denotes that a property is required._
 <Banner type="success">
   <strong>Tip:</strong>
   <br />
-  The <a href="/docs/getting-started/concepts#depth">Depth</a> parameter can be
-  used to automatically populate related documents that are returned by the API.
+  The [Depth](/docs/getting-started/concepts#depth) parameter can be used to
+  automatically populate related documents that are returned by the API.
 </Banner>
 
 ### Admin config

package/docs/fields/upload.mdx

@@ -6,13 +6,13 @@ desc: Upload fields will allow a file to be uploaded, only from a collection sup
 keywords: upload, images media, fields, config, configuration, documentation, Content Management System, cms, headless, javascript, node, react, express
 ---
 
-<Banner >
+<Banner>
   The Upload field allows for the selection of a Document from a collection supporting Uploads, and formats the selection as a thumbnail in the Admin panel.
 </Banner>
 
 <Banner type="warning">
-  <strong>Important:</strong><br/>
-  To use this field, you need to have a Collection configured to allow Uploads. For more information, <a href="/docs/upload/overview">click here</a> to read about how to enable Uploads on a collection by collection basis.
+  <strong>Important:</strong><br />
+  To use this field, you need to have a Collection configured to allow Uploads. For more information, [click here](/docs/upload/overview) to read about how to enable Uploads on a collection by collection basis.
 </Banner>
 
 **Example uses:**
@@ -23,10 +23,10 @@ keywords: upload, images media, fields, config, configuration, documentation, Co
 
 ### Config
 
-| Option           | Description                                                                                                                                                                                         |
-| ---------------- |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **`name`** *         | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                              |
-| **`*relationTo`** *  | Provide a single collection `slug` to allow this field to accept a relation to. <strong>Note: the related collection must be configured to support Uploads.</strong>                                |
+| Option               | Description                                                                                                                                                                                         |
+| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **`name`** \*        | To be used as the property name when stored and retrieved from the database. [More](/docs/fields/overview#field-names)                                                                              |
+| **`*relationTo`** \* | Provide a single collection `slug` to allow this field to accept a relation to. <strong>Note: the related collection must be configured to support Uploads.</strong>                                |
 | **`filterOptions`**  | A query to filter which options appear in the UI and validate against. [More](#filtering-upload-options).                                                                                           |
 | **`maxDepth`**       | Sets a number limit on iterations of related documents to populate when queried. [Depth](/docs/getting-started/concepts#depth)                                                                      |
 | **`label`**          | Text used as a field label in the Admin panel or an object with keys for each language.                                                                                                             |
@@ -41,28 +41,28 @@ keywords: upload, images media, fields, config, configuration, documentation, Co
 | **`localized`**      | Enable localization for this field. Requires [localization to be enabled](/docs/configuration/localization) in the Base config.                                                                     |
 | **`required`**       | Require this field to have a value.                                                                                                                                                                 |
 | **`admin`**          | Admin-specific configuration. See the [default field admin config](/docs/fields/overview#admin-config) for more details.                                                                            |
-| **`custom`**         | Extension point for adding custom data (e.g. for plugins) |
+| **`custom`**         | Extension point for adding custom data (e.g. for plugins)                                                                                                                                           |
 
-*\* An asterisk denotes that a property is required.*
+_\* An asterisk denotes that a property is required._
 
 ### Example
 
 `collections/ExampleCollection.ts`
+
 ```ts
-import { CollectionConfig } from 'payload/types';
+import { CollectionConfig } from "payload/types";
 
 export const ExampleCollection: CollectionConfig = {
-  slug: 'example-collection',
+  slug: "example-collection",
   fields: [
     {
-      name: 'backgroundImage', // required
-      type: 'upload', // required
-      relationTo: 'media', // required
+      name: "backgroundImage", // required
+      type: "upload", // required
+      relationTo: "media", // required
       required: true,
-    }
-  ]
-}
-
+    },
+  ],
+};
 ```
 
 ### Filtering upload options
@@ -71,23 +71,23 @@ Options can be dynamically limited by supplying a [query constraint](/docs/queri
 
 The `filterOptions` property can either be a `Where` query directly, or a function that returns one. When using a function, it will be called with an argument object with the following properties:
 
-| Property      | Description  |
-| ------------- | -------------|
-| `relationTo`       | The `relationTo` to filter against (as defined on the field) |
-| `data`             | An object of the full collection or global document currently being edited |
-| `siblingData`      | An object of the document data limited to fields within the same parent to the field |
-| `id`               | The value of the collection `id`, will be `undefined` on create request |
-| `user`             | The currently authenticated user object |
+| Property      | Description                                                                          |
+| ------------- | ------------------------------------------------------------------------------------ |
+| `relationTo`  | The `relationTo` to filter against (as defined on the field)                         |
+| `data`        | An object of the full collection or global document currently being edited           |
+| `siblingData` | An object of the document data limited to fields within the same parent to the field |
+| `id`          | The value of the collection `id`, will be `undefined` on create request              |
+| `user`        | The currently authenticated user object                                              |
 
 **Example:**
 
 ```ts
 const uploadField = {
-  name: 'image',
-  type: 'upload',
-  relationTo: 'media',
+  name: "image",
+  type: "upload",
+  relationTo: "media",
   filterOptions: {
-    mimeType: { contains: 'image' },
+    mimeType: { contains: "image" },
   },
 };
 ```
@@ -95,6 +95,6 @@ const uploadField = {
 You can learn more about writing queries [here](/docs/queries/overview).
 
 <Banner type="warning">
-  <strong>Note:</strong><br/>
+  <strong>Note:</strong><br />
   When an upload field has both <strong>filterOptions</strong> and a custom <strong>validate</strong> function, the api will not validate <strong>filterOptions</strong> unless you call the default upload field validation function imported from <strong>payload/fields/validations</strong> in your validate function.
 </Banner>

package/docs/graphql/overview.mdx

@@ -115,16 +115,8 @@ GraphQL Playground is enabled by default for development purposes, but disabled
 You can even log in using the `login[collection-singular-label-here]` mutation to use the Playground as an authenticated user.
 
 <Banner type="success">
-  <strong>Tip:</strong>
-  <br />
-  To see more regarding how the above queries and mutations are used, visit your
-  GraphQL playground (by default at{" "}
-  <a href="http://localhost:3000/api/graphql-playground">
-    (http://localhost:3000/api/graphql-playground
-  </a>
-  ) while your server is running. There, you can use the "Schema" and "Docs"
-  buttons on the right to see a ton of detail about how GraphQL operates within
-  Payload.
+  <strong>Tip:</strong><br />
+  To see more regarding how the above queries and mutations are used, visit your GraphQL playground (by default at [http://localhost:3000/api/graphql-playground](http://localhost:3000/api/graphql-playground)) while your server is running. There, you can use the "Schema" and "Docs" buttons on the right to see a ton of detail about how GraphQL operates within Payload.
 </Banner>
 
 ## Query complexity limits