@directus/app 9.0.0-rc.96 → 9.0.0

package/dist/assets/installation.6a1c6e0a.js

@@ -1,51 +0,0 @@
-var e=`# Installation
-
-> Directus can be installed in many different ways and on several different stacks. You can choose between local,
-> self-hosted on-premises, or our managed Cloud solution.
-
-While our CLI is the recommended method for self-hosting, you can use whichever of these self-hosted options best suits
-your needs. These methods offer a high level of customization and are ideal for intermediate developers.
-
-- [Command Line Interface (CLI)](/guides/installation/cli)
-- [Docker](/guides/installation/docker)
-- [Manually](/guides/installation/manual)
-
-::: tip Development Environment
-
-To work on the Directus Core source code, please follow our [Contributing Guide](/contributing/introduction).
-
-:::
-
-## Deployment Guides
-
-The following guides will walk you through the self-hosted installation process for specific third-party platforms.
-These options are only recommended for developers familiar with these services and comfortable with more advanced setup.
-While Directus is always completely free, you will likely need to pay for these services.
-
-- [Generic Ubuntu](/guides/installation/ubuntu)
-- [Internet Information Services (IIS)](/guides/installation/iis)
-- [Amazon AWS](/guides/installation/aws)
-- [DigitalOcean App Platform](/guides/installation/digitalocean-app-platform)
-- [Shared Hosting with Plesk](/guides/installation/plesk)
-
-## One-Click Installs
-
-If you would like to completely avoid the manual installation process, the following self-hosted one-click apps will
-handle the heavy-lifting for you. While Directus is always completely free, you will likely need to pay for these
-services.
-
-- [DigitalOcean](https://marketplace.digitalocean.com/apps/directus?action=deploy&refcode=4c0b6062c16e)
-- [Heroku](https://heroku.com/deploy?template=https://github.com/directus-community/heroku-template)
-- [Platform.sh](https://console.platform.sh/projects/create-project?template=https%3A%2F%2Fraw.githubusercontent.com%2Fplatformsh%2Ftemplate-builder%2Fmaster%2Ftemplates%2Fdirectus%2F.platform.template.yaml)
-- [Zeet](https://deploy.zeet.co/?url=https://github.com/directus-community/heroku-template)
-
-## Directus Cloud
-
-In addition to the self-hosted options above, you can also choose to create Directus projects using our official Managed
-Cloud Service. This is the easiest way to get up-and-running with Directus \u2014 even for non-technical users. Unique
-features include dedicated hardware, automatic updates, automatic backups, usage-based pricing, and more.
-
-- [Directus Cloud Dashboard](http://directus.cloud/)
-- [Learn more about On-Demand Cloud](https://directus.io/on-demand-cloud/)
-- [Learn more about Enterprise Cloud](https://directus.io/enterprise-cloud/)
-`;export{e as default};

package/dist/assets/interfaces.7e32c79b.js

@@ -1,125 +0,0 @@
-var e=`# Custom Interfaces <small></small>
-
-> Custom Interfaces allow you to create new ways of viewing or interacting with field data on the Item Detail page.
-> [Learn more about Interfaces](/concepts/interfaces/).
-
-## 1. Setup the Boilerplate
-
-Every interface is a standalone "package" that contains at least a metadata file and a Vue component. We recommend using
-the following file structure:
-
-\`\`\`
-src/
-	index.js
-	interface.vue
-\`\`\`
-
-### src/index.js
-
-\`\`\`js
-import InterfaceComponent from './interface.vue';
-
-export default {
-	id: 'custom',
-	name: 'Custom',
-	description: 'This is my custom interface!',
-	icon: 'box',
-	component: InterfaceComponent,
-	types: ['string'],
-};
-\`\`\`
-
-- \`id\` \u2014 The unique key for this interface. It is good practice to scope proprietary interfaces with an author prefix.
-- \`name\` \u2014 The human-readable name for this interface.
-- \`description\` \u2014 A short description (<80 characters) of this interface shown in the App.
-- \`icon\` \u2014 An icon name from the material icon set, or the extended list of Directus custom icons.
-- \`component\` \u2014 A reference to your Vue component.
-- \`types\` \u2014 An array of supported [types](/concepts/types/).
-- \`groups\` \u2014 An array of field-groups. Accepts \`standard\`, \`file\`, \`files\`, \`m2o\`, \`o2m\`, \`m2a\`, \`translations\`.
-  Defaults to \`standard\`.
-
-::: tip TypeScript
-
-See
-[the TypeScript definition](https://github.com/directus/directus/blob/20355fee5eba514dd75565f60269311187010c66/app/src/interfaces/types.ts#L5-L18)
-for more info on what can go into this object.
-
-:::
-
-### src/interface.vue
-
-\`\`\`vue
-<template>
-	<input :value="value" @input="handleChange($event.target.value)" />
-</template>
-
-<script>
-export default {
-	emits: ['input'],
-	props: {
-		value: String,
-	},
-	methods: {
-		handleChange(value) {
-			this.$emit('input', value);
-		},
-	},
-};
-<\/script>
-\`\`\`
-
-#### Available Props
-
-- \`value\` \u2014 The value of the field.
-- \`width\` \u2014 The layout width of the field. Either \`half\`, \`half-right\`, \`full\`, or \`fill\`.
-- \`type\` \u2014 The type of the field.
-- \`collection\` \u2014 The collection name of the field.
-- \`field\` \u2014 The key of the field.
-- \`primaryKey\` \u2014 The current item's primary key.
-
-## 2. Install Dependencies
-
-Set up a package.json file by running:
-
-\`\`\`bash
-npm init -y
-\`\`\`
-
-To be read by the Admin App, your custom interface's Vue component must first be bundled into a single \`index.js\` file.
-We recommend bundling your code using the directus-extension CLI from our \`@directus/extensions-sdk\` package. The CLI
-internally uses a Rollup configuration tailored specifically to bundling Directus extensions. To install the Extension
-SDK, run this command:
-
-\`\`\`bash
-npm i -D @directus/extensions-sdk
-\`\`\`
-
-For the directus-extension CLI to recognize the extension type, the input path and the output path, add this field to
-the root of the \`package.json\` file:
-
-\`\`\`json
-"directus:extension": {
-	"type": "interface",
-	"path": "dist/index.js",
-	"source": "src/index.js",
-	"host": "^9.0.0-rc.87",
-	"hidden": false
-}
-\`\`\`
-
-## 3. Develop your Custom Interface
-
-The interface itself is simply a Vue component, which provides an blank canvas for creating anything you need.
-
-## 4. Build and Deploy
-
-To build the interface for use within Directus, run:
-
-\`\`\`bash
-npx directus-extension build
-\`\`\`
-
-Finally, move the output from your interface's \`dist\` folder into your project's
-\`/extensions/interfaces/my-custom-interface\` folder. Keep in mind that the extensions directory is configurable within
-your env file, and may be located elsewhere.
-`;export{e as default};

package/dist/assets/interfaces.d4446a7e.js

@@ -1,46 +0,0 @@
-var e=`# Interfaces <small></small>
-
-> Interfaces determine how you view or interact with a field. In most cases, they offer some sort of input tailored to
-> managing data of a specific type, but can also be used exclusively for presentation.
-
-Interfaces provide different ways to view or interact with field data on the
-[Item Detail](/concepts/application/#item-detail) page's form. Every interface supports a specific subset of field
-[types](/concepts/types/) (eg: String), which determines how the data will be stored. For example, the _Text Input_
-interface can manage most types of data, but might not be ideal for dates, where a _Calendar_ interface excels.
-
-Directus includes many Interfaces out-of-the-box, below are the some key examples:
-
-- **Checkboxes**
-- **Code**
-- **Color**
-- **DateTime**
-- **Divider**
-- **Dropdown**
-- **File**
-- **Image**
-- **Many-to-Many**
-- **Many-to-One**
-- **Markdown**
-- **Notice**
-- **Numeric**
-- **One-to-Many**
-- **Radio Buttons**
-- **Repeater**
-- **Slider**
-- **Tags**
-- **Text Input**
-- **Textarea**
-- **Toggle**
-- **Translations**
-- **WYSIWYG**
-
-## Custom Interface Extensions
-
-In addition to these core interfaces, custom interfaces allow for creating more tailored or proprietary ways to view or
-manage field data, such as bespoke layout builders, skeuomorphic knobs, or relational views for third-party data (eg:
-Stripe Credit Card UI).
-
-#### Relevant Guides
-
-- [Creating a Custom Interface](/guides/interfaces)
-`;export{e as default};

package/dist/assets/introduction.2964a2db.js

@@ -1,259 +0,0 @@
-var e=`# API Reference
-
-> Directus offers both a RESTful and GraphQL API to manage the data in the database. The API has predictable
-> resource-oriented URLs, relies on standard HTTP status codes, and uses JSON for input and output.
-
-::: tip Dynamic I/O
-
-Since most endpoints return data based on your specific schema and configured permissions, the input/output of the API
-differs greatly for individual installations.
-
-:::
-
-[[toc]]
-
-## REST vs. GraphQL
-
-**There is no difference in the functionality available between the REST and GraphQL endpoints.** The functionality
-available in both is mapped to same set of core services, meaning that you don't lose any performance or capabilities by
-choosing one or the other.
-
-Which one you choose is ultimately up to you.
-
-## Authentication
-
-By default, all data in the system is off limits for unauthenticated users. To gain access to protected data, you must
-[include an access token with every request](/reference/api/authentication/), or
-[configure permissions for the public role](/concepts/roles/#public-role).
-
-Useful references:
-
-- [Authenticating into the API](/reference/api/authentication/)
-- [Login endpoint reference](/reference/api/system/authentication/)
-
-## Relational Data
-
-Directus only retrieves the fields in your items that explicitly have been requested. Relational data can be retrieved
-nested by using the [the \`fields\` parameter](/reference/api/query/#fields) in REST, or regular nested queries in
-GraphQL. This allows you to retrieve the author of your article included in the articles data, or fetch related log
-entry points for your app's analytics data for example.
-
-### Creating / Updating / Deleting
-
-Similarly to fetching, relational content can be modified deeply as well.
-
-#### Many-to-One
-
-Many-to-One relationships are fairly straightforward to manage relationally. You can simply submit the changes you want
-as an object under the relational key in your collection. For example, if you wanted to create a new featured article on
-your page, you could submit:
-
-\`\`\`json
-{
-	"featured_article": {
-		"title": "This is my new article!"
-	}
-}
-\`\`\`
-
-This will create a new record in the related collection, and save its primary key in the \`featured_article\` field for
-this item. To update an existing item, simply provide the primary key with the updates, and Directus will treat it as an
-update instead of a creation:
-
-\`\`\`json
-{
-	"featured_article": {
-		"id": 15,
-		"title": "This is an updated title for my article!"
-	}
-}
-\`\`\`
-
-Seeing that the Many-to-One relationship stores the foreign key on the field itself, removing the item can be done by
-nullifying the field:
-
-\`\`\`json
-{
-	"featured_article": null
-}
-\`\`\`
-
-#### One-to-Many (/ Many-to-Many)
-
-One-to-Many, and therefore Many-to-Many and Many-to-Any, relationships can be updated in one of two ways:
-
-**Basic**
-
-The API will return one-to-many fields as an array of nested keys or items (based on the \`fields\` parameter). You can
-use this same structure to select what the related items are:
-
-\`\`\`json
-{
-	"children": [2, 7, 149]
-}
-\`\`\`
-
-You can also provide an object instead of a primary key in order to create new items nested on the fly, or an object
-with a primary key included to update an existing item:
-
-\`\`\`json
-{
-	"children": [
-		2, // assign existing item 2 to be a child of the current item
-		{
-			"name": "A new nested item"
-		},
-		{
-			"id": 149,
-			"name": "Assign and update existing item 149"
-		}
-	]
-}
-\`\`\`
-
-To remove items from this relationship, simply omit them from the array:
-
-\`\`\`json
-{
-	"children": [2, 149]
-}
-\`\`\`
-
-This method of updating a one-to-many is very useful for smaller relational datasets.
-
-**"Detailed"**
-
-Alternatively, you can provide an object detailing the changes as follows:
-
-\`\`\`json
-{
-	"children": {
-		"create": [{ "name": "A new nested item" }],
-		"update": [{ "id": 149, "name": "A new nested item" }],
-		"delete": [7]
-	}
-}
-\`\`\`
-
-This is useful if you need to have more tightly control on staged changes, or when you're working with a big relational
-dataset.
-
-#### Many-to-Any (Union Types)
-
-Many-to-Any fields work very similar to a "regular" many-to-many, with the exception that the related field can pull in
-the fields from any of the related collections, for example:
-
-\`\`\`json
-{
-	"sections": [
-		{
-			"collection": "headings",
-			"item": {
-				/* headings fields */
-			}
-		},
-		{
-			"collection": "paragraphs",
-			"item": {
-				/* paragraphs fields */
-			}
-		}
-	]
-}
-\`\`\`
-
-##### REST API
-
-To scope the fields that are returned per collection type, you can use the \`<field>:<scope>\` syntax in the fields
-parameter as follows:
-
-\`\`\`
-GET /items/pages
-	?fields[]=sections.item:headings.id
-	&fields[]=sections.item:headings.title
-	&fields[]=sections.item:paragraphs.body
-	&fields[]=sections.item:paragraphs.background_color
-\`\`\`
-
-##### GraphQL
-
-In GraphQL, you can use nested fragments on the Union Type to select the fields:
-
-\`\`\`graphql
-query {
-	pages {
-		sections {
-			item {
-				... on headings {
-					id
-					title
-				}
-
-				... on paragraphs {
-					body
-					background_color
-				}
-			}
-		}
-	}
-}
-\`\`\`
-
-::: tip Updating
-
-Updating records in a many-to-any is identical to the other relationship types.
-
-:::
-
-## SEARCH HTTP Method
-
-When using the REST API to read multiple items by (very) advanced filters, you might run into the issue where the URL
-simply can't hold enough data to include the full query structure. In those cases, you can use the SEARCH http method as
-a drop-in replacement for GET, where you're allowed to put the query into the request body as follows:
-
-**Before:**
-
-\`\`\`
-GET /items/articles?filter[title][_eq]=Hello World
-\`\`\`
-
-**After:**
-
-\`\`\`json
-SEARCH /items/articles
-
-{
-	"query": {
-		"filter": {
-			"title": {
-				"_eq": "Hello World"
-			}
-		}
-	}
-}
-\`\`\`
-
-There's a lot of discussion around whether or not to put a body in a GET request, to use POSTs to create search queries,
-or to rely on a different method altogether. As of right now, we've chosen
-[to align with IETF's _HTTP SEARCH Method_ specification](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/).
-While we recognize this is still a draft spec, the SEARCH method has been used extensively before in the WebDAV world
-([spec](https://tools.ietf.org/html/rfc5323)), and compared to the other available options, it feels like the "cleanest"
-and most correct to handle this moving forward. As with everything else, if you have any ideas, opinions, or concerns,
-[we'd love to hear your thoughts](http://github.com/directus/directus/discussions/new).
-
-Useful reading:
-
-- [_HTTP SEARCH Method_ (IETF, 2021)](https://datatracker.ietf.org/doc/draft-ietf-httpbis-safe-method-w-body/)
-- [_Defining a new HTTP method: HTTP SEARCH_ (Tim Perry, 2021)](https://httptoolkit.tech/blog/http-search-method/)
-- [_HTTP GET with request body_ (StackOverflow, 2009 and ongoing)](https://stackoverflow.com/questions/978061/http-get-with-request-body)
-- [_Elastic Search GET body usage_ (elastic, n.d.)](https://www.elastic.co/guide/en/elasticsearch/guide/current/_empty_search.html)
-- [_Dropbox starts using POST, and why this is poor API design._ (Evert Pot, 2015)](https://evertpot.com/dropbox-post-api/)
-
-## System data in GraphQL
-
-Due to restrictions in GraphQL itself, it's impossible to properly scope/namespace system functionality from regular
-data access. In order to prevent any naming conflicts between user-created and system data, we've scoped the access to
-the two into two endpoints for user and system data respectively: \`/graphql\` and \`/graphql/system\`. Both endpoints share
-the same underlying schema, so **nested relations will work as expected** regardless if they "cross over" between user
-and system data. The only difference in the two endpoints are the root query and mutation fields available.
-`;export{e as default};

package/dist/assets/introduction.7c47e334.js

@@ -1,152 +0,0 @@
-var e=`# Contributing
-
-> Our team truly appreciates every single contributor, community member, GitHub star, pull-request, bug report, and
-> feature request. Keeping Directus completely free and open-source is our way of saying: **Thank you!**
-
-::: tip We're here to help!
-
-If you have _any_ questions along your contributor journey, please feel free to come chat with us on our
-[Discord Community](https://directus.chat).
-
-:::
-
-## Code of Conduct
-
-**The Directus [Code of Conduct](https://github.com/directus/directus/blob/main/code_of_conduct.md) is one of the ways
-we put our values into practice. We expect all of our staff, contractors and contributors to know and follow this
-code.**
-
-**Our contributors and maintainers work extremely hard to build Directus as premium open-source software. Please be
-respectful of those efforts throughout our ecosystem. Trolling, harassing, insulting, or other unacceptable behavior by
-participants will not be tolerated.**
-
-In the interest of fostering an open and welcoming environment, we as pledge to make participation in our project and
-community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex
-characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality,
-personal appearance, race, religion, or sexual identity and orientation.
-
-Examples of behavior that contributes to creating a positive environment include:
-
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-
-**Before continuing, please take a moment to read our full
-[Code of Conduct](https://github.com/directus/directus/blob/main/contributing.md).**
-
-## Wait \u2014 Before you Begin
-
-When contributing to this repository, it is important to first discuss the change you wish to make with the owners of
-this repository. This can be done via [GitHub Issue](https://github.com/directus/directus/issues),
-[GitHub Discussions](https://github.com/directus/directus/discussions), [Discord](https://directus.chat),
-[email](mailto:info@directus.io), or any other method.
-
-Following this rule will help avoid wasted time caused by multiple people working on the same issue or writing code that
-will not be merged.
-
-## Feature Requests
-
-Feature requests are a great way to let our team know what should be prioritized next. You can
-[submit a new feature request](https://github.com/directus/directus/discussions/category_choices) or
-[vote on existing submissions](https://github.com/directus/directus/discussions) via GitHub Discussions.
-
-::: warning The 80/20 Rule
-
-To keep the Directus codebase as clean and simple as possible, we will only consider approving features that we feel at
-least 80% of our user-base will find valuable. If your feature request falls within the 20% range, it is considered an
-edge-case and should be implemented as an extension.
-
-:::
-
-## RFCs
-
-Some Directus features/fixes may require additional design, strategy, and/or discussion before beginning work. For these
-notable pull-requests, you should first submit an RFC (Request For Comments) to our core team via
-[Discord](https://directus.chat). This process is relatively informal, but ensures proper alignment, and helps avoid
-squandered development time by contributors.
-
-## Bug Reporting
-
-Reporting any bugs you come across is an invaluable part of helping keep Directus stable. After confirming a similar
-issue doesn't already exist, you can [submit a bug report](https://github.com/directus/directus/issues/new) via GitHub
-Issues. Please ensure the following for all submissions:
-
-- You are experiencing an actual bug, not a configuration issue
-- You are using the official (pre-built) version of directus and not a fork
-- You are not asking a question or requesting a new feature
-- You have checked that no similar issue already exists
-- You have entered a clear and concise title
-- You have followed the issue template, with stack details and steps to reproduce
-- You have already completed all [troubleshooting steps](/getting-started/support#troubleshooting-steps)
-
-## Reporting Security Vulnerabilities
-
-If you believe you have discovered a security issue within a Directus product or service, please reach out to us
-directly over email: [security@directus.io](mailto:security@directus.io). We will then open a
-[GitHub Security Advisory](https://github.com/directus/directus/security/advisories) for tracking the fix.
-
-We value the members of the independent security research community who find security vulnerabilities and work with our
-team so that proper fixes can be issued to users. Our policy is to credit all researchers in the fix's release notes. In
-order to receive credit, security researchers must follow responsible disclosure practices, including:
-
-- They do not publish the vulnerability prior to the Directus team releasing a fix for it
-- They do not divulge exact details of the issue, eg: through exploits or proof-of-concepts
-
-## Submitting a Pull-Request
-
-### 1. Submit an RFC (if needed)
-
-Please read our docs on the [RFC process](#rfcs).
-
-### 2. Update relevant docs
-
-Before submitting any pull-requests, ensure that any relevant documentation (included in this same repo) is updated.
-
-### 3. Push your changes
-
-\`\`\`bash
-git push -u origin YOUR-BRANCH-NAME
-\`\`\`
-
-### Submit a pull-request
-
-Once you push the changes to your repo, the "Compare & pull request" button will appear in GitHub. Click it and you'll
-be taken to a screen where you can fill in the appropriate details. Finally, open the pull request by clicking the
-"Create pull request" button.
-
-Now our core staff will review your contribution and either merge it, or request that you to make changes.
-
-## Syncing Your Fork with Directus
-
-After you have submitted your pull requests, you would need to sync your fork with Directus to pull all the latest
-commits before you continue to contribute.
-
-### 1. Add Directus as a Remote
-
-While your fork is your main remote or origin, you will add Directus as the upstream, which generally refers to the
-original repo that you have forked.
-
-\`\`\`bash
-git remote add upstream git@github.com:directus/directus.git
-\`\`\`
-
-### 2. Fetch the Latest Changes
-
-Depending on your setup, you will need to get the latest commits from the \`main\` branch of Directus by doing a pull,
-reset, rebase or fetch.
-
-\`\`\`bash
-git pull upstream main
-\`\`\`
-
-At this point you are ready to continue working on Directus, with the latest commits included!
-
-::: tip
-
-Before you begin or resume development, be sure to always sync, if you are going to submit a pull request with your
-changes!
-
-:::
-`;export{e as default};