@directus/app 9.0.0-rc.96 → 9.0.0-rc.97

package/dist/assets/presets.0b1a4454.js

@@ -1,625 +0,0 @@
-var n=`---
-pageClass: page-reference
----
-
-# Preset
-
-<div class="two-up">
-<div class="left">
-
-> Presets hold the preferences of individual users of the platform. This allows Directus to show and maintain custom
-> item listings and bookmarks for users of the app.
-> [Learn more about Presets](/concepts/collections/#collection-presets-bookmarks).
-
-</div>
-<div class="right">
-
-[[toc]]
-
-</div>
-</div>
-
----
-
-## The Preset Object
-
-<div class="two-up">
-<div class="left">
-<div class="definitions">
-
-\`id\` **uuid**\\
-Primary key of the preset.
-
-\`bookmark\` **string**\\
-The title of the bookmark. If this value is \`null\`, it's considered a preset instead of a bookmark.
-
-\`user\` **many-to-one**\\
-User this preset applies to. Many-to-one to [users](/reference/api/system/users/).
-
-\`role\` **many-to-one**\\
-Role this preset applies to. Many-to-one to [users](/reference/api/system/roles/).
-
-\`collection\` **string**\\
-Collection this preset applies to.
-
-\`search\` **string**\\
-The search query used in the preset.
-
-\`filters\` **array**\\
-The filters used in the preset.
-
-\`layout\` **string**\\
-The layout used in this preset.
-
-\`layout_query\` **object**\\
-The item query used by the layout. This structure is based on the used layout.
-
-\`layout_options\` **object**\\
-The options used by the layout. This structure is based on the used layout.
-
-</div>
-</div>
-<div class="right">
-
-\`\`\`json
-{
-	"id": 39,
-	"bookmark": null,
-	"user": "410b5772-e63f-4ae6-9ea2-39c3a31bd6ca",
-	"role": null,
-	"collection": "directus_activity",
-	"search": null,
-	"filters": [],
-	"layout": "tabular",
-	"layout_query": {
-		"tabular": {
-			"sort": "-timestamp",
-			"fields": ["action", "collection", "timestamp", "user"],
-			"page": 1
-		}
-	},
-	"layout_options": {
-		"tabular": {
-			"widths": {
-				"action": 100,
-				"collection": 210,
-				"timestamp": 240,
-				"user": 240
-			}
-		}
-	}
-}
-\`\`\`
-
-</div>
-</div>
-
----
-
-## List Presets
-
-List all presets that exist in Directus.
-
-<div class="two-up">
-<div class="left">
-
-::: tip Permissions
-
-The data returned in this endpoint will be filtered based on the user's permissions. For example, presets for a role
-other than the current user's role won't be returned.
-
-:::
-
-### Query Parameters
-
-Supports all [global query parameters](/reference/api/query).
-
-### Returns
-
-An array of up to [limit](/reference/api/query/#limit) [preset objects](#the-preset-object). If no items are available,
-data will be an empty array.
-
-</div>
-<div class="right">
-
-### REST API
-
-\`\`\`
-GET /presets
-SEARCH /presets
-\`\`\`
-
-[Learn more about SEARCH ->](/reference/api/introduction/#search-http-method)
-
-### GraphQL
-
-\`\`\`
-POST /graphql/system
-\`\`\`
-
-\`\`\`graphql
-type Query {
-	presets: [directus_presets]
-}
-\`\`\`
-
-##### Example
-
-\`\`\`graphql
-query {
-	presets {
-		id
-		user
-	}
-}
-\`\`\`
-
-</div>
-</div>
-
----
-
-## Retrieve a preset
-
-List an existing preset by primary key.
-
-<div class="two-up">
-<div class="left">
-
-### Query Parameters
-
-Supports all [global query parameters](/reference/api/query).
-
-### Returns
-
-Returns the requested [preset object](#the-preset-object).
-
-</div>
-<div class="right">
-
-### REST API
-
-\`\`\`
-GET /presets/:id
-\`\`\`
-
-##### Example
-
-\`\`\`
-GET /presets/42
-\`\`\`
-
-### GraphQL
-
-\`\`\`
-POST /graphql/system
-\`\`\`
-
-\`\`\`graphql
-type Query {
-	presets_by_id(id: ID!): directus_presets
-}
-\`\`\`
-
-##### Example
-
-\`\`\`graphql
-query {
-	presets_by_id(id: 42) {
-		id
-		user
-	}
-}
-\`\`\`
-
-</div>
-</div>
-
----
-
-## Create a Preset
-
-Create a new preset.
-
-<div class="two-up">
-<div class="left">
-
-### Query Parameters
-
-Supports all [global query parameters](/reference/api/query).
-
-### Request Body
-
-A partial [preset object](#the-preset-object).
-
-### Returns
-
-Returns the [preset object](#the-preset-object) for the created preset.
-
-</div>
-<div class="right">
-
-### REST API
-
-\`\`\`
-POST /presets
-\`\`\`
-
-##### Example
-
-\`\`\`json
-// POST /presets
-
-{
-	"user": "410b5772-e63f-4ae6-9ea2-39c3a31bd6ca",
-	"layout": "cards",
-	"search": "Directus"
-}
-\`\`\`
-
-### GraphQL
-
-\`\`\`
-POST /graphql/system
-\`\`\`
-
-\`\`\`graphql
-type Mutation {
-	create_presets_item(data: create_directus_presets_input!): directus_presets
-}
-\`\`\`
-
-##### Example
-
-\`\`\`graphql
-mutation {
-	create_presets_item(data: { user: "410b5772-e63f-4ae6-9ea2-39c3a31bd6ca", layout: "cards", search: "Directus" }) {
-		id
-		user
-	}
-}
-\`\`\`
-
-</div>
-</div>
-
----
-
-## Create Multiple Presets
-
-Create multiple new presets.
-
-<div class="two-up">
-<div class="left">
-
-### Query Parameters
-
-Supports all [global query parameters](/reference/api/query).
-
-### Request Body
-
-An array of partial [preset objects](#the-preset-object).
-
-### Returns
-
-Returns the [preset object](#the-preset-object) for the created preset.
-
-</div>
-<div class="right">
-
-### REST API
-
-\`\`\`
-POST /presets
-\`\`\`
-
-##### Example
-
-\`\`\`json
-// POST /presets
-
-[
-	{
-		"collection": "directus_files",
-		"user": "410b5772-e63f-4ae6-9ea2-39c3a31bd6ca",
-		"layout": "cards",
-		"search": "Directus"
-	},
-	{
-		"collection": "articles",
-		"user": "410b5772-e63f-4ae6-9ea2-39c3a31bd6ca",
-		"layout": "tabular"
-	}
-]
-\`\`\`
-
-### GraphQL
-
-\`\`\`
-POST /graphql/system
-\`\`\`
-
-\`\`\`graphql
-type Mutation {
-	create_presets_items(data: [create_directus_presets_input!]!): [directus_presets]
-}
-\`\`\`
-
-##### Example
-
-\`\`\`graphql
-mutation {
-	create_presets_items(
-		data: [
-			{
-				collection: "directus_files"
-				user: "410b5772-e63f-4ae6-9ea2-39c3a31bd6ca"
-				layout: "cards"
-				search: "Directus"
-			}
-			{ collection: "articles", user: "410b5772-e63f-4ae6-9ea2-39c3a31bd6ca", layout: "tabular" }
-		]
-	) {
-		id
-		user
-	}
-}
-\`\`\`
-
-</div>
-</div>
-
----
-
-## Update a Preset
-
-Update an existing preset.
-
-<div class="two-up">
-<div class="left">
-
-### Query Parameters
-
-Supports all [global query parameters](/reference/api/query).
-
-### Request Body
-
-A partial [preset object](#the-preset-object).
-
-### Returns
-
-Returns the [preset object](#the-preset-object) for the updated preset.
-
-</div>
-<div class="right">
-
-### REST API
-
-\`\`\`
-PATCH /presets/:id
-\`\`\`
-
-##### Example
-
-\`\`\`json
-// PATCH /presets/34
-
-{
-	"layout": "tabular"
-}
-\`\`\`
-
-### GraphQL
-
-\`\`\`
-POST /graphql/system
-\`\`\`
-
-\`\`\`graphql
-type Mutation {
-	update_presets_item(id: ID!, data: update_directus_presets_input): directus_presets
-}
-\`\`\`
-
-##### Example
-
-\`\`\`graphql
-mutation {
-	update_presets_item(id: 32, data: { layout: "tabular" }) {
-		id
-		user
-	}
-}
-\`\`\`
-
-</div>
-</div>
-
----
-
-## Update Multiple Presets
-
-Update multiple existing presets.
-
-<div class="two-up">
-<div class="left">
-
-### Query Parameters
-
-Supports all [global query parameters](/reference/api/query).
-
-### Request Body
-
-<div class="definitions">
-
-\`keys\` **Required**\\
-Array of primary keys of the presets you'd like to update.
-
-\`data\` **Required**\\
-Any of [the preset object](#the-preset-object)'s properties.
-
-</div>
-
-### Returns
-
-Returns the [preset objects](#the-preset-object) for the updated presets.
-
-</div>
-<div class="right">
-
-### REST API
-
-\`\`\`
-PATCH /presets
-\`\`\`
-
-##### Example
-
-\`\`\`json
-// PATCH /presets
-
-{
-	"keys": [15, 64],
-	"data": {
-		"layout": "tabular"
-	}
-}
-\`\`\`
-
-### GraphQL
-
-\`\`\`
-POST /graphql/system
-\`\`\`
-
-\`\`\`graphql
-type Mutation {
-	update_presets_items(ids: [ID!]!, data: update_directus_presets_input): [directus_presets]
-}
-\`\`\`
-
-##### Example
-
-\`\`\`graphql
-mutation {
-	update_presets_items(ids: [15, 64], data: { layout: "tabular" }) {
-		id
-		user
-	}
-}
-\`\`\`
-
-</div>
-</div>
-
----
-
-## Delete a Preset
-
-Delete an existing preset.
-
-<div class="two-up">
-<div class="left">
-
-### Returns
-
-Empty body.
-
-</div>
-<div class="right">
-
-### REST API
-
-\`\`\`
-DELETE /presets/:id
-\`\`\`
-
-##### Example
-
-\`\`\`
-DELETE /presets/34
-\`\`\`
-
-### GraphQL
-
-\`\`\`
-POST /graphql/system
-\`\`\`
-
-\`\`\`graphql
-type Mutation {
-	delete_presets_item(id: ID!): delete_one
-}
-\`\`\`
-
-##### Example
-
-\`\`\`graphql
-mutation {
-	delete_presets_item(id: 32) {
-		id
-	}
-}
-\`\`\`
-
-</div>
-</div>
-
----
-
-## Delete Multiple Presets
-
-Delete multiple existing presets.
-
-<div class="two-up">
-<div class="left">
-
-### Request Body
-
-An array of preset primary keys
-
-### Returns
-
-Empty body.
-
-</div>
-<div class="right">
-
-### REST API
-
-\`\`\`
-DELETE /presets
-\`\`\`
-
-##### Example
-
-\`\`\`json
-// DELETE /presets
-[15, 251, 810]
-\`\`\`
-
-### GraphQL
-
-\`\`\`
-POST /graphql/system
-\`\`\`
-
-\`\`\`graphql
-type Mutation {
-	delete_presets_items(ids: [ID!]!): delete_many
-}
-\`\`\`
-
-##### Example
-
-\`\`\`graphql
-mutation {
-	delete_presets_items(ids: [15, 251, 810]) {
-		ids
-	}
-}
-\`\`\`
-
-</div>
-</div>
-`;export{n as default};

package/dist/assets/presets.582eb0e2.js

@@ -1,58 +0,0 @@
-var e=`# Collection Presets
-
-> Presets store the state of a Collection Detail page. They can be used to set layout defaults or define bookmarks to
-> specific datasets. [Learn more about Presets](/concepts/presets/).
-
-## Creating a Preset
-
-1. Navigate to **Settings > Presets & Bookmarks**
-2. Click the **Create Preset** action button in the header
-3. Complete the **other preset form fields** outlined below
-
-- **Collection** \u2014 The collection of this preset; supports any project collection, Directus Files, or Directus Users
-- **Scope** \u2014 The users that will have access to this preset, either Global, a specific Role, or an individual User
-- **Layout** \u2014 The collection detail's layout this preset applies to
-- **Name** \u2014 If left blank, this preset will act as a Default for the collection/layout; if given a name, it will be
-  shown as a bookmark
-
-After you have completed the form, the layout preview will be populated with live data. You can now tailor the layout as
-desired by updating the preview or the filter component in the page sidebar.
-
-Each preset saves all of the information needed to recreate a view of the collection/layou, including: the full-text
-search query, any advanced filters added, sort field, sort direction, and all other specific layout options.
-
-::: tip Defaults vs Bookmarks
-
-It's important to be aware of the difference between a collection's _defaults_ and its _bookmarks_, both of which are
-configured by presets. A _default_ is how a user will initially view the collection detail without any further
-customization, while a _bookmark_ is a named dataset that can be recalled at any point via the
-[collection navigation](/guides/roles/#customizing-the-collection-navigation).
-
-:::
-
-::: tip System Defaults
-
-You can also adjust the defaults and bookmarks for the Directus Activity, Directus Files, and Directus Users
-collections.
-
-:::
-
-::: tip Order of Defaults
-
-Multiple defaults can be configured for a user, either for different layouts of even the same layout. In this case, the
-preset priority is: User, then Role, then Global.
-
-:::
-
-## Deleting a Preset
-
-1. Navigate to **Settings > Presets & Bookmarks > [Preset]**
-2. Click the red **Delete Preset** action button in the header
-3. Confirm this decision by clicking **Delete** in the dialog
-
-::: danger Irreversible Change
-
-This action is permanent and can not be undone. Please proceed with caution.
-
-:::
-`;export{e as default};

package/dist/assets/projects.a52ff43f.js

@@ -1,40 +0,0 @@
-var e=`# Projects
-
-> A Project is a complete instance of Directus. Each project represents a **Database**, but also encapsulates a config
-> file, asset storage, and any custom extensions.
-
-Projects are the highest level of structure in Directus. While there are many customizable facets to a Project, you can
-essentially think of them as individual [Databases](concepts/databases/).
-
-#### Relevant Guides
-
-- [Creating a Project](/guides/projects/#creating-a-project)
-- [Configuring a Project](/guides/projects/#configuring-a-project)
-- [Adjusting Project Settings](/guides/projects/#adjusting-project-settings)
-- [Upgrading a Project](/guides/projects/#upgrading-a-project)
-- [Backing-up a Project](/guides/projects/#backing-up-a-project)
-- [Migrating a Project](/guides/projects/#migrating-a-project)
-- [Deleting a Project](/guides/projects/#configuring-a-project)
-
-## Environments
-
-This compartmentalized approach means you can also create different Environments (eg: Dev, Staging, Prod) simply by
-creating additional Project instances. In short, there is no difference between a Project and an Environment.
-
-#### Relevant Guides
-
-- [Migrating a Project](/guides/projects/#migrating-a-project)
-
-## Multitenancy
-
-Previous versions of Directus allowed managing multiple databases within a single installation. However this because
-overly complex in the scoping of routes, API endpoints, and custom code. In Directus 9+, to create multitenancy you have
-several options:
-
-- **Project Scoping** \u2014 Creating a super-admin layer that provisions new tenant projects has been made easier by the
-  Cloud-native model of Directus 9+. This method involves developing custom code that can dynamically spin up/down
-  projects, but is also the most flexible, supporting scoped extensions and differentiated project settings.
-- **Role Scoping** \u2014 In this method, you create one Role per tenant, and configure their permissions to properly scope
-  them within a single project. This direction allows for tenants to share a single schema using _item_ scoped
-  permissions, or different schemas by using _collection_ scoped permissions.
-`;export{e as default};