payload 0.15.1 → 0.15.4

package/docs/fields/relationship.mdx

@@ -22,6 +22,7 @@ keywords: relationship, fields, config, configuration, documentation, Content Ma
 | ---------------- | ----------- |
 | **`name`** *         | To be used as the property name when stored and retrieved from the database.  |
 | **`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. |
 | **`maxDepth`**       | Sets a number limit on iterations of related documents to populate when queried. [Depth](/docs/getting-started/concepts#depth) |
 | **`label`**          | Used as a field label in the Admin panel and to name the generated GraphQL type. |
@@ -44,6 +45,50 @@ keywords: relationship, fields, config, configuration, documentation, Content Ma
   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.
 </Banner>
 
+### Filtering relationship options
+
+Options can be dynamically limited by supplying a [query constraint](/docs/queries/overview), which will be used both for validating input and filtering available relationships in the UI.
+
+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 |
+
+**Example:**
+
+```js
+  const relationshipField = {
+    name: 'purchase',
+    type: 'relationship',
+    relationTo: ['products', 'services'],
+    filterOptions: ({ relationTo, siblingData }) => {
+      // returns a Where query dynamically by the type of relationship
+      if (relationTo === 'products') {
+        return {
+          'stock': { is_greater_than: siblingData.quantity }
+        }
+      }
+
+      if (relationTo === 'services') {
+        return {
+          'isAvailable': { equals: true }
+        }
+      }
+    },
+  };
+```
+
+You can learn more about writing queries [here](/docs/queries/overview).
+
+<Banner type="warning">
+  When a relationship field has both <strong>filterOptions</strong> and a custom <strong>validate</strong> function, the server-side validation will not enforce <strong>filterOptions</strong>unless you call the default relationship field validation function imported from <strong>payload/fields/validations</strong> within your custom function.
+</Banner>
+
 ### How the data is saved
 
 Given the variety of options possible within the `relationship` field type, the shape of the data needed for creating and updating these fields can vary. The following sections will describe the variety of data shapes that can arise from this field.

package/docs/fields/upload.mdx

@@ -27,6 +27,7 @@ keywords: upload, images media, fields, config, configuration, documentation, Co
 | ---------------- | ----------- |
 | **`name`** *         | To be used as the property name when stored and retrieved from the database.  |
 | **`*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-relationship-options). |
 | **`maxDepth`**       | Sets a number limit on iterations of related documents to populate when queried. [Depth](/docs/getting-started/concepts#depth) |
 | **`label`**          | Used as a field label in the Admin panel and to name the generated GraphQL type. |
 | **`unique`**         | Enforce that each entry in the Collection has a unique value for this field. |

package/docs/getting-started/installation.mdx

@@ -88,15 +88,19 @@ app.listen(3000, async () => {
 
 ```
 
-As you can see above, the required arguments to the `init` function are as follows:
+Here is a list of all properties available to pass through `payload.init`:
+
+##### `express`
+
+**Required**. This is your Express app as shown above. Payload will tie into your existing `app` and scope all of its functionalities to sub-routers. By default, Payload will add an `/admin` router and an `/api` router, but you can customize these paths.
 
 ##### `secret`
 
-This is a secure string that will be used to authenticate with Payload. It can be random but should be at least 14 characters and be very difficult to guess. Often, it's smart to store this value in an `env` and set different values for each of your environments (local, stage, prod, etc). The `dotenv` package is very handy and works well alongside of Payload.
+**Required**. This is a secure string that will be used to authenticate with Payload. It can be random but should be at least 14 characters and be very difficult to guess. Often, it's smart to store this value in an `env` and set different values for each of your environments (local, stage, prod, etc). The `dotenv` package is very handy and works well alongside of Payload.
 
 ##### `mongoURL`
 
-This is a fully qualified MongoDB connection string that points to your Mongo database. If you don't have Mongo installed locally, you can [follow these steps for Mac OSX](https://docs.mongodb.com/manual/tutorial/install-mongodb-on-os-x/) and [these steps](https://docs.mongodb.com/manual/tutorial/install-mongodb-on-windows/) for Windows 10. If you want to use a local database and you know you have MongoDB installed locally, a typical connection string will look like this:
+**Required**. This is a fully qualified MongoDB connection string that points to your Mongo database. If you don't have Mongo installed locally, you can [follow these steps for Mac OSX](https://docs.mongodb.com/manual/tutorial/install-mongodb-on-os-x/) and [these steps](https://docs.mongodb.com/manual/tutorial/install-mongodb-on-windows/) for Windows 10. If you want to use a local database and you know you have MongoDB installed locally, a typical connection string will look like this:
 
 `mongodb://localhost/payload`
 
@@ -104,11 +108,7 @@ In contrast to running Mongo locally, a popular option is to sign up for a free
 
 ##### `mongoOptions`
 
-An optional object to customize connection options. Payload will connect to your MongoDB database using default options which you can override and extend to include all the [options](https://mongoosejs.com/docs/connections.html#options) available to mongoose.
-
-##### `express`
-
-This is your Express app as shown above. Payload will tie into your existing `app` and scope all of its functionalities to sub-routers. By default, Payload will add an `/admin` router and an `/api` router, but you can customize these paths.
+Customize Mongo connection options. Payload will connect to your MongoDB database using default options which you can override and extend to include all the [options](https://mongoosejs.com/docs/connections.html#options) available to mongoose.
 
 ##### `license`
 
@@ -116,15 +116,19 @@ Your Payload license key. Not needed for development purposes, but when it's tim
 
 ##### `email`
 
-An Optional object used to configure SMTP. [Read more](/docs/email/overview).
+An object used to configure SMTP. [Read more](/docs/email/overview).
 
 ##### `local`
 
 A boolean that when set to `true` tells Payload to start in local-only mode which will bypass setting up API routes. When set to `true`, `express` is not required. This is useful when running scripts that need to use Payload's [local-api](/docs/local-api/overview).
 
+##### `loggerOptions`
+
+Specify options for the built-in Pino logger that Payload uses for internal logging. See [Pino Docs](https://getpino.io/#/docs/api?id=options) for more info on what is available.
+
 ##### `onInit`
 
-An optional function that is called immediately following startup that receives the Payload instance as it's only argument.
+A function that is called immediately following startup that receives the Payload instance as it's only argument.
 
 ### Test it out
 

package/docs/queries/overview.mdx

@@ -59,7 +59,8 @@ The above example demonstrates a simple query but you can get much more complex.
 | `greater_than_equal` | For numeric or date-based fields. |
 | `less_than`          | For numeric or date-based fields. |
 | `less_than_equal`    | For numeric or date-based fields. |
-| `like`               | The value must partially match. |
+| `like`               | Case-insensitive string must be present. If string of words, all words must be present, in any order. |
+| `contains`           | Must contain the value entered, case-insensitive. |
 | `in`                 | The value must be found within the provided comma-delimited list of values. |
 | `not_in`             | The value must NOT be within the provided comma-delimited list of values. |
 | `exists`             | Only return documents where the value either exists (`true`) or does not exist (`false`). |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "payload",
-  "version": "0.15.1",
+  "version": "0.15.4",
   "description": "Node, React and MongoDB Headless CMS and Application Framework",
   "license": "SEE LICENSE IN license.md",
   "author": {