@directus/app 9.0.0-rc.96 → 9.0.0

package/dist/assets/api-config.6e53e3a6.js

@@ -1,180 +0,0 @@
-var e=`# Configuring the API
-
-[[toc]]
-
-## Cache
-
-Directus has a built-in way to do data-caching. Enabling this will cache the output of the request (based on the current
-user and exact query parameters used) into to configured cache storage location. This will drastically improve API
-performance, as subsequent requests are served straight from this cache. Enabling cache will also make Directus return
-accurate cache-control headers. Depending on your setup, this will further improve performance by caching the request in
-middleman servers (like CDNs) and even the browser.
-
-You can enable the data-cache with the \`CACHE_ENABLED\` environment variable.
-
-### Cache Store
-
-In bigger projects, you most likely don't want to rely on local memory to keep the caches. Instead, you can use the
-\`CACHE_STORE\` environment variable to tell Directus to use either \`memcache\` or \`redis\` to store the caches.
-
-\`\`\`
-CACHE_ENABLED="true"
-
-CACHE_STORE="redis"
-CACHE_REDIS="redis://@127.0.0.1"
-\`\`\`
-
-### Auto-Purging
-
-Directus can automatically clear the caches whenever a create/update/delete action is performed. This allows you to keep
-the Directus API real-time, while still getting the performance benefits on quick subsequent reads.
-
-\`\`\`
-CACHE_AUTO_PURGE="true"
-\`\`\`
-
-### TTL
-
-Based on your project's needs, you might be able to aggressively cache your data, only requiring new data to be fetched
-every hour or so. This allows you to squeeze the most performance out of your Directus instance. This can be incredibly
-useful for applications where you have a lot of (public) read-access and where updates aren't real-time (for example a
-website). \`CACHE_TTL\` uses [\`ms\`](https://www.npmjs.com/package/ms) to parse the value, so you configure it using human
-readable values (like \`2 days\`, \`7 hrs\`, \`5m\`).
-
-\`\`\`
-CACHE_TTL="1h"
-\`\`\`
-
-### Assets
-
-The cache-control header for the /assets endpoint is separate from the regular data-cache. This is useful as it's often
-possible to cache assets for way longer than you would with the actual content.
-
-\`\`\`
-ASSETS_CACHE_TTL="7d"
-\`\`\`
-
-## oAuth (Single Sign-On (SSO) / OpenID)
-
-Directus' oAuth integration provides a powerful alternative way to authenticate into your project. Directus will ask you
-to login on the external service, and if your user exists in Directus, you'll be logged in automatically.
-
-Directus relies on [\`grant\`](https://www.npmjs.com/package/grant) for the handling of the oAuth flow. This means that
-there's hundreds of services that are supported out of the box. For example, enabling logging in through GitHub is as
-easy as creating an [oAuth app in GitHub](https://github.com/settings/developers) and adding the following to Directus:
-
-\`\`\`
-OAUTH_PROVIDERS="github"
-OAUTH_GITHUB_KEY="99d3...c3c4"
-OAUTH_GITHUB_SECRET="34ae...f963"
-\`\`\`
-
-::: warning PUBLIC_URL
-
-The oAuth flow relies on the \`PUBLIC_URL\` variable for it's redirecting. Make sure that variable is configured
-correctly.
-
-:::
-
-#### Multiple Providers
-
-\`OAUTH_PROVIDERS\` accepts a CSV of providers, allowing you to specify multiple at the same time:
-
-\`\`\`
-OAUTH_PROVIDERS ="google,microsoft"
-
-OAUTH_GOOGLE_KEY = "<google_application_id>"
-OAUTH_GOOGLE_SECRET=  "<google_application_secret_key>"
-OAUTH_GOOGLE_SCOPE="openid email"
-
-OAUTH_MICROSOFT_KEY = "<microsoft_application_id>"
-OAUTH_MICROSOFT_SECRET = "<microsoft_application_secret_key>"
-OAUTH_MICROSOFT_SCOPE = "openid email"
-OAUTH_MICROSOFT_AUTHORIZE_URL = "https://login.microsoftonline.com/<microsoft_application_id>/oauth2/v2.0/authorize"
-OAUTH_MICROSOFT_ACCESS_URL = "https://login.microsoftonline.com/<microsoft_application_id>/oauth2/v2.0/token"
-
-PUBLIC_URL = "<public_url_of_directus_instance>"
-\`\`\`
-
-### Provider Specific Configuration
-
-If you use one of the many supported providers, you often don't have to configure any more than just the key and secret
-for the service. That being said, if you use a more tailored service (like the specific Microsoft application in the
-example above), you might have to provide more configuration values yourself. Please see
-https://github.com/simov/grant#configuration-description for a list of all available configuration flags.
-
-## File Storage
-
-By default, Directus stores every file you upload locally on disk. Instead of local file storage, you can configure
-Directus to use S3 or Google Cloud Storage instead:
-
-\`\`\`
-STORAGE_LOCATIONS="aws"
-
-STORAGE_AWS_DRIVER="s3"
-STORAGE_AWS_KEY="tp15c...510vk"
-STORAGE_AWS_SECRET="yk29b...b932n"
-STORAGE_AWS_REGION="us-east-2"
-STORAGE_AWS_BUCKET="my-files"
-\`\`\`
-
-### Multiple Storage Adapters
-
-You can configure multiple storage adapters at the same time. This allows you to choose where files are being uploaded
-on a file-by-file basis. To do this, you can provide a CSV of storage location names, and provide a config block for
-each of them:
-
-\`\`\`
-STORAGE_LOCATIONS="local,aws"
-
-STORAGE_LOCAL_DRIVER="local"
-STORAGE_LOCAL_ROOT="local"
-
-STORAGE_AWS_KEY="tp15c...510vk"
-STORAGE_AWS_SECRET="yk29b...b932n"
-STORAGE_AWS_REGION="us-east-2"
-STORAGE_AWS_BUCKET="my-files"
-\`\`\`
-
-In the Admin App, files will automatically be uploaded to the first configured storage location (in this case \`local\`).
-The used storage location is saved under \`storage\` in \`directus_files\`.
-
-## Rate Limiting
-
-You can use the built-in rate-limiter to prevent users from hitting the API too much. To enable the rate-limiter, simply
-set
-
-\`\`\`
-RATE_LIMITER_ENABLED="true"
-\`\`\`
-
-This will kick-in the rate-limiter on a maximum of 50 requests a second. You can configure this using:
-
-\`\`\`
-// 10 requests per 5 seconds
-
-RATE_LIMITER_POINTS="10"
-RATE_LIMITER_DURATION="5"
-\`\`\`
-
-Once you have multiple copies of Directus running under a load-balancer, or your user base grows so much that memory is
-no longer a viable place to store the rate limiter information, you can use an external \`memcache\` or \`redis\` instance
-to store the rate limiter data:
-
-\`\`\`
-RATE_LIMITER_ENABLED="true"
-
-RATE_LIMITER_POINTS="10"
-RATE_LIMITER_DURATION="5"
-
-RATE_LIMITER_STORE="redis"
-
-RATE_LIMITER_REDIS="redis://@127.0.0.1"
-\`\`\`
-
-## File-Based Configuration
-
-In case you prefer using a configuration file instead of environment variables, you can use the \`CONFIG_PATH\`
-environment variable to instruct Directus to use a local configuration file instead of environment variables. See
-[Config Files](/reference/config-files.md) for more information.
-`;export{e as default};

package/dist/assets/api-endpoints.4b802644.js

@@ -1,74 +0,0 @@
-var e=`# Custom API Endpoints <small></small>
-
-> Custom API Endpoints register new API routes which can be used to infinitely extend the core functionality of the
-> platform.
-
-## 1. Setup the Boilerplate
-
-Custom endpoints are dynamically loaded from within your project's \`/extensions/endpoints\` folder. Keep in mind that the
-extensions directory is configurable within your env file, and may be located elsewhere.
-
-Each endpoint is registered using a registration function within a scoped directory. For example, to create a custom
-\`/my-endpoint/\` endpoint, you would add the following function to \`/extensions/endpoints/my-endpoint/index.js\`.
-
-\`\`\`js
-module.exports = function registerEndpoint(router) {
-	router.get('/', (req, res) => res.send('Hello, World!'));
-};
-\`\`\`
-
-You can also create several scoped endpoints within a single function:
-
-\`\`\`js
-// /my-endpoint/
-// /my-endpoint/intro
-// /my-endpoint/goodbye
-module.exports = function registerEndpoint(router) {
-	router.get('/', (req, res) => res.send('Hello, World!'));
-	router.get('/intro', (req, res) => res.send('Nice to meet you.'));
-	router.get('/goodbye', (req, res) => res.send('Goodbye!'));
-};
-\`\`\`
-
-## 2. Develop your Custom Endpoint
-
-The \`registerEndpoint\` function receives two parameters: \`router\` and \`context\`. Router is an express Router instance
-that is scoped to \`/<extension-name>\`, while \`context\` holds the following properties:
-
-- \`services\` \u2014 All API internal services.
-- \`exceptions\` \u2014\xA0API exception objects that can be used to throw "proper" errors.
-- \`database\` \u2014 Knex instance that is connected to the current database.
-- \`getSchema\` \u2014 Async function that reads the full available schema for use in services
-- \`env\` \u2014\xA0Parsed environment variables.
-- \`logger\` \u2014\xA0[Pino](https://github.com/pinojs/pino) instance.
-
-## 3. Restart the API
-
-To deploy your endpoint, simply restart the API by running:
-
-\`\`\`bash
-npx directus start
-\`\`\`
-
-## Full Example:
-
-\`\`\`js
-// extensions/endpoints/recipes/index.js
-
-module.exports = function registerEndpoint(router, { services, exceptions }) {
-	const { ItemsService } = services;
-	const { ServiceUnavailableException } = exceptions;
-
-	router.get('/', (req, res, next) => {
-		const recipeService = new ItemsService('recipes', { schema: req.schema, accountability: req.accountability });
-
-		recipeService
-			.readByQuery({ sort: [{ column: 'name', order: 'asc' }], fields: ['*'] })
-			.then((results) => res.json(results))
-			.catch((error) => {
-				return next(new ServiceUnavailableException(error.message));
-			});
-	});
-};
-\`\`\`
-`;export{e as default};

package/dist/assets/api-hooks.722161c6.js

@@ -1 +0,0 @@
-var e="# Custom API Hooks <small></small>\n\n> Custom API Hooks allow running custom logic when a specified event occurs within your project. They can be registered\n> as either \"blocking\" or immediate.\n\n## 1. Create a Hook File\n\nCustom hooks are dynamically loaded from within your extensions folder. By default this directory is located at\n`/extensions`, but it can be configured within your project's env file to be located anywhere.\n\n### Default Standalone Hook Location\n\n```\n/extensions/hooks/<hook-id>/index.js\n```\n\n## 2. Define the Event\n\nNext, you will want to define your event. You can trigger your custom hook with any of the platform's many API events.\nSystem events are referenced with the format:\n\n```\n<scope>.<action>(.<before>)\n// eg: items.create\n// eg: files.create\n// eg: collections.*\n// eg: users.update.before\n```\n\n### Scope\n\nThe scope determines the API endpoint that is triggered. The `*` wildcard can also be used to include all scopes.\n\n::: tip System Scope\n\nCurrently all system tables are available as event scopes except for `directus_migrations` and `directus_sessions`,\nwhich don't have relevant endpoints or services.\n\n:::\n\n### Action\n\nDefines the triggering operation within the specified context (see chart below). The `*` wildcard can also be used to\ninclude all actions available to the scope.\n\n### Before\n\nMany scopes (see chart below) support an optional `.before` suffix for running a _blocking_ hook prior to the event\nbeing fired. This allows you to check and/or modify the event's payload before it is processed.\n\n- `items.create.before` (Blocking)\n- `items.create` (Non Blocking, also called 'after' implicitly)\n\nThis also allows you to cancel an event based on the logic within the hook. Below is an example of how you can cancel a\ncreate event by throwing a standard Directus exception.\n\n```js\nmodule.exports = function registerHook({ exceptions }) {\n	const { InvalidPayloadException } = exceptions;\n\n	return {\n		'items.create.before': async function (input) {\n			if (LOGIC_TO_CANCEL_EVENT) {\n				throw new InvalidPayloadException(WHAT_IS_WRONG);\n			}\n\n			return input;\n		},\n	};\n};\n```\n\n### Event Format Options\n\n| Scope                           | Actions                                                            | Before           |\n| ------------------------------- | ------------------------------------------------------------------ | ---------------- |\n| `cron()`                        | [See below for configuration](#interval-cron)                      | No               |\n| `cli.init`                      | `before` and `after`                                               | No               |\n| `server`                        | `start` and `stop`                                                 | Optional         |\n| `init`                          |                                                                    | Optional         |\n| `routes.init`                   | `before` and `after`                                               | No               |\n| `routes.custom.init`            | `before` and `after`                                               | No               |\n| `middlewares.init`              | `before` and `after`                                               | No               |\n| `request`                       | `not_found`                                                        | No               |\n| `response`                      |                                                                    | No<sup>[1]</sup> |\n| `database.error`                | When a database error is thrown                                    | No               |\n| `error`                         |                                                                    | No               |\n| `auth`                          | `login`, `logout`<sup>[1]</sup>, `jwt` and `refresh`<sup>[1]</sup> | Optional         |\n| `oauth.:provider`<sup>[2]</sup> | `login` and `redirect`                                             | Optional         |\n| `items`                         | `read`<sup>[3]</sup>, `create`, `update` and `delete`              | Optional         |\n| `activity`                      | `create`, `update` and `delete`                                    | Optional         |\n| `collections`                   | `create`, `update` and `delete`                                    | Optional         |\n| `fields`                        | `create`, `update` and `delete`                                    | Optional         |\n| `files`                         | `upload`<sup>[3]</sup>                                             | No               |\n| `folders`                       | `create`, `update` and `delete`                                    | Optional         |\n| `permissions`                   | `create`, `update` and `delete`                                    | Optional         |\n| `presets`                       | `create`, `update` and `delete`                                    | Optional         |\n| `relations`                     | `create`, `update` and `delete`                                    | Optional         |\n| `revisions`                     | `create`, `update` and `delete`                                    | Optional         |\n| `roles`                         | `create`, `update` and `delete`                                    | Optional         |\n| `settings`                      | `create`, `update` and `delete`                                    | Optional         |\n| `users`                         | `create`, `update` and `delete`                                    | Optional         |\n| `webhooks`                      | `create`, `update` and `delete`                                    | Optional         |\n\n<sup>1</sup> Feature Coming Soon\\\n<sup>2</sup> oAuth provider name can replaced with wildcard for any oauth providers `oauth.*.login`\\\n<sup>3</sup> Doesn't support `.before` modifier\n\n#### Interval (cron)\n\nHooks support running on an interval through [`node-cron`](https://www.npmjs.com/package/node-cron). To set this up,\nprovide a cron statement in the event scope as follows: `cron(<statement>)`, for example `cron(15 14 1 * *)` (at 14:15\non day-of-month 1) or `cron(5 4 * * sun)` (at 04:05 on Sunday). See example below:\n\n```js\nconst axios = require('axios');\n\nmodule.exports = function registerHook() {\n	return {\n		'cron(*/15 * * * *)': async function () {\n			await axios.post('http://example.com/webhook', { message: 'Another 15 minutes passed...' });\n		},\n	};\n};\n```\n\n## 3. Register your Hook\n\nEach custom hook is registered to its event scope using a function with the following format:\n\n```js\nconst axios = require('axios');\n\nmodule.exports = function registerHook() {\n	return {\n		'items.create': function () {\n			axios.post('http://example.com/webhook');\n		},\n	};\n};\n```\n\n## 4. Develop your Custom Hook\n\n> Hooks can impact performance when not carefully implemented. This is especially true for `before` hooks (as these are\n> blocking) and hooks on `read` actions, as a single request can result in a large amount of database reads.\n\n### Register Function\n\nThe register function (eg: `module.exports = function registerHook()`) must return an object where the key is the event,\nand the value is the handler function itself.\n\nThe `registerHook` function receives a context parameter with the following properties:\n\n- `services` \u2014 All API internal services\n- `exceptions` \u2014\xA0API exception objects that can be used for throwing \"proper\" errors\n- `database` \u2014 Knex instance that is connected to the current database\n- `getSchema` \u2014 Async function that reads the full available schema for use in services\n- `env` \u2014\xA0Parsed environment variables\n- `logger` \u2014\xA0[Pino](https://github.com/pinojs/pino) instance.\n\n### Event Handler Function\n\nThe event handler function (eg: `'items.create': function()`) receives a context parameter with the following\nproperties:\n\n- `event` \u2014 Full event string\n- `accountability` \u2014 Information about the current user\n- `collection` \u2014 Collection that is being modified\n- `item` \u2014\xA0Primary key(s) of the item(s) being modified\n- `action`\xA0\u2014 Action that is performed\n- `payload` \u2014\xA0Payload of the request\n- `schema` - The current API schema in use\n- `database` - Current database transaction\n\n::: tip Input\n\nThe `items.*.before` hooks get the raw input payload as the first parameter, with the context parameter as the second\nparameter.\n\n:::\n\n#### Items read\n\nIn contrast to the other `items` events (`items.create`, `items.update`, `items.delete`) the `items.read` doesn't\nreceive the primary key(s) of the items but the query used:\n\n- `event` \u2014 Full event string\n- `accountability` \u2014 Information about the current user\n- `collection` \u2014 Collection that is being modified\n- `query` \u2014\xA0The query used to get the data\n- `action`\xA0\u2014 Action that is performed\n- `payload` \u2014\xA0Payload of the request\n- `schema` - The current API schema in use\n- `database` - Current database transaction\n\n#### Auth\n\nThe `auth` and `oauth` hooks have the following context properties:\n\n- `event` \u2014 Full event string\n- `accountability` \u2014 Information about the current user\n- `action`\xA0\u2014 Action that is performed\n- `payload` \u2014\xA0Payload of the request\n- `schema` - The current API schema in use\n- `status` - One of `pending`, `success`, `fail`\n- `user` <sup>\u2020</sup> - ID of the user that tried logging in/has logged in\n\n<sup>\u2020</sup> Not available in `oauth`\n\n## 5. Restart the API\n\nTo deploy your hook, simply restart the API by running:\n\n```bash\nnpx directus start\n```\n\n## Full Example\n\n`extensions/hooks/sync-with-external/index.js`:\n\n```js\nconst axios = require('axios');\n\nmodule.exports = function registerHook({ services, exceptions }) {\n	const { MailService } = services;\n	const { ServiceUnavailableException, ForbiddenException } = exceptions;\n\n	return {\n		// Force everything to be admin-only at all times\n		'items.*': async function ({ item, accountability }) {\n			if (accountability.admin !== true) throw new ForbiddenException();\n		},\n		// Sync with external recipes service, cancel creation on failure\n		'items.create.before': async function (input, { collection, schema }) {\n			if (collection !== 'recipes') return input;\n\n			const mailService = new MailService({ schema });\n\n			try {\n				await axios.post('https://example.com/recipes', input);\n				await mailService.send({\n					to: 'person@example.com',\n					template: {\n						name: 'item-created',\n						data: {\n							collection: collection,\n						},\n					},\n				});\n			} catch (error) {\n				throw new ServiceUnavailableException(error);\n			}\n\n			input[0].syncedWithExample = true;\n\n			return input;\n		},\n	};\n};\n```\n";export{e as default};

package/dist/assets/apl.18e81a50.js

@@ -1 +0,0 @@
-import{bz as h}from"./vendor.90d6ad72.js";function g(i,o){return o.forEach(function(t){Object.keys(t).forEach(function(l){if(l!=="default"&&!(l in i)){var u=Object.getOwnPropertyDescriptor(t,l);Object.defineProperty(i,l,u.get?u:{enumerable:!0,get:function(){return t[l]}})}})}),Object.freeze(i)}var f={exports:{}};(function(i,o){(function(t){t(h.exports)})(function(t){t.defineMode("apl",function(){var l={".":"innerProduct","\\":"scan","/":"reduce","\u233F":"reduce1Axis","\u2340":"scan1Axis","\xA8":"each","\u2363":"power"},u={"+":["conjugate","add"],"\u2212":["negate","subtract"],"\xD7":["signOf","multiply"],"\xF7":["reciprocal","divide"],"\u2308":["ceiling","greaterOf"],"\u230A":["floor","lesserOf"],"\u2223":["absolute","residue"],"\u2373":["indexGenerate","indexOf"],"?":["roll","deal"],"\u22C6":["exponentiate","toThePowerOf"],"\u235F":["naturalLog","logToTheBase"],"\u25CB":["piTimes","circularFuncs"],"!":["factorial","binomial"],"\u2339":["matrixInverse","matrixDivide"],"<":[null,"lessThan"],"\u2264":[null,"lessThanOrEqual"],"=":[null,"equals"],">":[null,"greaterThan"],"\u2265":[null,"greaterThanOrEqual"],"\u2260":[null,"notEqual"],"\u2261":["depth","match"],"\u2262":[null,"notMatch"],"\u2208":["enlist","membership"],"\u2377":[null,"find"],"\u222A":["unique","union"],"\u2229":[null,"intersection"],"\u223C":["not","without"],"\u2228":[null,"or"],"\u2227":[null,"and"],"\u2371":[null,"nor"],"\u2372":[null,"nand"],"\u2374":["shapeOf","reshape"],",":["ravel","catenate"],"\u236A":[null,"firstAxisCatenate"],"\u233D":["reverse","rotate"],"\u2296":["axis1Reverse","axis1Rotate"],"\u2349":["transpose",null],"\u2191":["first","take"],"\u2193":[null,"drop"],"\u2282":["enclose","partitionWithAxis"],"\u2283":["diclose","pick"],"\u2337":[null,"index"],"\u234B":["gradeUp",null],"\u2352":["gradeDown",null],"\u22A4":["encode",null],"\u22A5":["decode",null],"\u2355":["format","formatByExample"],"\u234E":["execute",null],"\u22A3":["stop","left"],"\u22A2":["pass","right"]},s=/[\.\/⌿⍀¨⍣]/,c=/⍬/,p=/[\+−×÷⌈⌊∣⍳\?⋆⍟○!⌹<≤=>≥≠≡≢∈⍷∪∩∼∨∧⍱⍲⍴,⍪⌽⊖⍉↑↓⊂⊃⌷⍋⍒⊤⊥⍕⍎⊣⊢]/,d=/←/,v=/[⍝#].*$/,x=function(n){var r;return r=!1,function(e){return r=e,e===n?r==="\\":!0}};return{startState:function(){return{prev:!1,func:!1,op:!1,string:!1,escape:!1}},token:function(n,r){var e,a;return n.eatSpace()?null:(e=n.next(),e==='"'||e==="'"?(n.eatWhile(x(e)),n.next(),r.prev=!0,"string"):/[\[{\(]/.test(e)?(r.prev=!1,null):/[\]}\)]/.test(e)?(r.prev=!0,null):c.test(e)?(r.prev=!1,"niladic"):/[¯\d]/.test(e)?(r.func?(r.func=!1,r.prev=!1):r.prev=!0,n.eatWhile(/[\w\.]/),"number"):s.test(e)?"operator apl-"+l[e]:d.test(e)?"apl-arrow":p.test(e)?(a="apl-",u[e]!=null&&(r.prev?a+=u[e][1]:a+=u[e][0]),r.func=!0,r.prev=!1,"function "+a):v.test(e)?(n.skipToEnd(),"comment"):e==="\u2218"&&n.peek()==="."?(n.next(),"function jot-dot"):(n.eatWhile(/[\w\$_]/),r.prev=!0,"keyword"))}}}),t.defineMIME("text/apl","apl")})})();var m=f.exports,b=Object.freeze(g({__proto__:null,[Symbol.toStringTag]:"Module",default:m},[f.exports]));export{b as a};

package/dist/assets/app.3a60dc84.js

@@ -1 +0,0 @@
-var e="# App Reference\n\nThe purpose of the app reference is to allow more and easier access to our internal components when developing custom\ninterfaces, displays or modules.\n\n## App Structure\n\nThe Vue frontend app is structured into many departments to combine similar purpose components.\n\n| Folder        | Content                                                                                               | Example                                                                                     |\n| ------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |\n| `components`  | In here are our base components that are designed to be as general and everywhere fitting as possible | It contains `v-button`                                                                      |\n| `composables` | Composables are reusable pieces of logic that can be used inside Vue component                        | `use-shortcut` to easily react to button combinations pressed                               |\n| `directives`  | Directives are functions that are available on Vue components in templates                            | contains `v-focus` or `v-tooltip`                                                           |\n| `displays`    | Displays are functions / components that are used in the system to display data                       | `display-image` is used to display image data inside the app                                |\n| `interfaces`  | Interfaces are the individual blocks that allow editing and viewing individual pieces of data         | `interface-color` is a color picker allowing for easy selection of any color                |\n| `lang`        | Containing all translations used across the directus app                                              | Contains translations like `en-US`                                                          |\n| `layouts`     | Layouts change the way items are represented inside the collection view                               | The card and tabular layout are inside here                                                 |\n| `modules`     | Modules organize in which major parts the app is structured                                           | Here are the files or settings module which are always visible from the sidebar             |\n| `routes`      | Basic routes the app needs that shouldn't be customized                                               | Routes for authentication or password reset                                                 |\n| `stores`      | Here lay all stores used in the app containing all relevant data that gets fetched from the api       | The `fields` store containing all accessible fields for the user                            |\n| `styles`      | All general styles, css-vars, mixins and themes are stored inside here                                | The `form-grid` mixin allowing to style form like grids                                     |\n| `types`       | Contains types used to generalize data for typescript                                                 | `field-schema` which is used to model the schema of fields                                  |\n| `utils`       | Utility functions that helps minimize repetition                                                      | `notify` which is used to easily generate notifications inside the app                      |\n| `views`       | Views are the top-level parent component that are used in all modules                                 | `private-view` which renders the basic structure like sidebar, headers and content sections |\n";export{e as default};

package/dist/assets/application.a6a125c0.js

@@ -1,180 +0,0 @@
-var e=`# The Directus Application
-
-> The Directus App is the presentation layer for your data, content, and assets. It uses a left-to-right visual
-> hierarchy for organization and navigation. Below we cover the App's global elements and individual pages.
-
-The Directus App is decoupled from, and powered by, the Directus API. It provides a way for both technical admins and
-non-technical users to view and manage content of the connected database. It is written in [Vue.js](https://vuejs.org),
-is completely modular, and is highly customizable.
-
-## App Section Hierarchy
-
-![Application Overview](../assets/app-overview.svg)
-
-### 1. Module Bar
-
-- **Project Logo** \u2014 Displays your configured project logo and project color (defaults to the Directus logo and color).
-  If configured, clicking this component will navigate to the Project URL. During platform activity, an indeterminate
-  progress indicator will also be shown here.
-- **Module Navigation** \u2014 Allows navigating between the different modules your user has access to. Customizing the
-  Module Navigation is done within the [Role's configuration](/guides/roles/#configuring-a-role), but the default module
-  list includes:
-  - [Collections](#collections)
-  - [User Directory](#user-directory)
-  - [File Library](#file-library)
-  - [Documentation](#documentation)
-  - [Settings](#settings) (Admin Roles Only)
-  - [Any Custom Modules](/concepts/modules/) (Only if Configured)
-- **Current User Menu** \u2014 This component displays the authenticated user's name and avatar.
-  - Sign Out \u2014 Hovering over the User Menu exposes the button to log out of the platform.
-
-### 2. Navigation Bar
-
-- **Project Name** \u2014 Shows an icon and tooltip indicating the API's connection strength, and the name of your current
-  project, which can be configured under [Project Settings](/guides/projects/#adjusting-project-settings).
-- **Navigation** \u2014 This is a dynamic navigation based on your current module. Some modules also support
-  [Bookmark Presets](/guides/presets/#creating-a-preset), which are a customizable links to specific data-sets.
-
-### 3. Page
-
-- **Header** \u2014 A fixed section at the top of each page, the header includes:
-  - Page Icon \u2014 Clicking this navigates back to the previous page.
-  - Module Name \u2014 Clicking this navigates to the parent module/section.
-  - Page Title \u2014 Displays dynamic title of the current page.
-  - Action Buttons \u2014 Right-aligned contextual buttons for specific page actions.
-- **Page Content** \u2014 This displays the content of the page you navigated to.
-
-### 4. Page Sidebar
-
-- **Page Components** \u2014 Lists any contextual page components available. The "Info" component is available on every page,
-  explaining the page's general purpose and relevant details. Clicking any sidebar component will accordion it open. If
-  the App window is large enough, the sidebar will automatically open, and can be closed by clicking the "X" in the
-  top-right.
-- **Notifications Tray** \u2014 Fixed to the bottom of the page sidebar, this button opens a tray of recent user
-  notifications, and provides a link to the [Activity Log](#activity-log) page.
-
-## Collections
-
-This module is the primary way for interacting with your database content. Here you can access your collections, browse
-their items, and navigate to individual item forms.
-
-### Collection Listing
-
-A page that lists the collections available to the current user. This is the landing page of the module, and effectively
-the same as its navigation listing.
-
-### Collection Detail
-
-This is the main gateway to your content items, providing a highly configurable Layout for browsing and visualizing the
-items within a collection. The header of this page includes key action buttons for creating, deleting, and batch editing
-items.
-
-- [Adjusting a Collection Layout](/guides/collections/#adjusting-a-collection-layout)
-- [Creating an Item](/guides/items/#creating-an-item)
-- [Updating an Item](/guides/items/#updating-an-item)
-- [Deleting an Item](/guides/items/#deleting-an-item)
-- [Archiving an Item](/guides/items/#archiving-an-item)
-- [Ordering Items](/guides/items/#ordering-items)
-- [Exporting Items](/guides/items/#exporting-items)
-- Browsing Items
-  - [Searching](/guides/items/#searching-items)
-  - [Filtering](/guides/items/#filtering-items)
-  - [Bookmarking](/guides/items/#bookmarking-item-presets)
-
-### Item Detail
-
-Most Collection Detail Layouts support navigating to individual item detail pages where you a presented with a
-[customizable form](/guides/fields#adjusting-field-arrangement) for viewing/editing the item's content. Like other
-detail pages, there are many available features, including:
-
-- [Adjusting Field Arrangement](/guides/fields/#adjusting-field-arrangement)
-- [Updating an Item](/guides/items/#updating-an-item)
-- [Archiving an Item](/guides/items/#archiving-an-item)
-- [Reverting an Item](/guides/items/#reverting-an-item)
-- [Deleting an Item](/guides/items/#deleting-an-item)
-- [Commenting on an Item](/guides/items/#commenting-on-an-item)
-
-## User Directory
-
-This module includes a comprehensive listing of all system users within your project. This page has the same features
-and configuration as [Collection Detail](#collection-detail).
-
-### User Detail
-
-Similar to other [Item Detail](#item-detail) pages, this page provides a custom form for viewing system users. This is
-also used for editing the "Profile Page" of the current user, which is accessible from the [User Menu](#_1-module-bar).
-There are a number of [User Fields](/concepts/users/#user-fields) included out-of-the-box that can then be extended by
-following the normal [Creating a Field](/guides/fields/#creating-a-field) guide.
-
-- [Creating a User](/guides/users/#creating-a-user)
-- [Inviting a User](/guides/users/#inviting-a-user)
-- [Configuring a User](/guides/users/#configuring-a-user)
-- [Archiving a User](/guides/users/#archiving-a-user)
-- [Deleting a User](/guides/users/#deleting-a-user)
-
-## File Library
-
-This module aggregates all files within the project into one consolidated library. This page has the same features and
-configuration as [Collection Detail](#collection-detail).
-
-### File Detail
-
-Similar to other [Item Detail](#item-detail) pages, this page provides a custom form for viewing assets and embeds.
-There are a number of [File Fields](/concepts/files/#file-fields) included out-of-the-box that can then be extended by
-following the normal [Creating a Field](/guides/fields/#creating-a-field) guide.
-
-- [Uploading a File](/guides/files/#uploading-a-file)
-- [Accessing an Original File](/guides/files/#downloading-an-original-file)
-- [Creating a Thumbnail Preset](/guides/files/#creating-a-thumbnail-preset)
-- [Requesting a Thumbnail](/guides/files/#requesting-a-thumbnail)
-
-## Documentation
-
-This module is an internal set of guides, concepts, and reference docs for your project's specific version of Directus.
-It also includes a dynamic [API Reference](/reference/api/introduction) that is dynamically tailored to your custom
-schema. The docs are organized into these distinct sections:
-
-- [Getting Started](/getting-started/introduction/) \u2014 Novice oriented, for a platform intro and installation.
-- [Concepts](/concepts/activity) \u2014 Learning oriented, for understanding the platform.
-- [Guides](/guides/api-config) \u2014 Problem oriented, follow along with steps while working.
-- [Reference](/reference/command-line-interface) \u2014 Information oriented, look up info and specs while working.
-- [API Reference](/reference/api/introduction/) \u2014 Information oriented, look up API resources while working.
-- [Contributing](/contributing/introduction/) \u2014 Contributor oriented \u2014 resources for working on Open-Source Core.
-
-::: tip Updating the Docs
-
-Our docs are written in markdown (with some additional VuePress styling like this hint box), and available for
-editing/fixing via [GitHub](https://github.com/directus/directus).
-
-:::
-
-::: tip Public Docs
-
-The latest version of the Directus Docs are also available publicly. This online version includes additional sections,
-such as how to install the platform. [https://docs.directus.io](https://docs.directus.io)
-
-:::
-
-## Activity Log
-
-This module provides a collective timeline of all actions taken within the project. This is a great way to audit user
-activity or enforce accountability. This is the only system module that is not in the module bar by default \u2014 instead
-being located within the notifications tray of the page sidebar. This page has the same features and configuration as
-[Collection Detail](#collection-detail).
-
-### Activity Detail
-
-Unlike other item detail pages, activity items are **readonly** (for proper accountability) and open in a side drawer to
-display the [Activity Fields](/concepts/activity/#activity-fields).
-
-## Settings
-
-This module is only available to users within [Admin roles](/concepts/roles/#administrators-role). This is where your
-project is configured, and the first place to go after installation. It includes the following sections:
-
-- [Project Settings](/guides/projects/#adjusting-project-settings)
-- [Data Model](/concepts/databases/#database-mirroring)
-- [Roles & Permissions](/concepts/roles)
-- [Presets & Bookmarks](/concepts/collections/#collection-presets-bookmarks)
-- [Webhooks](/guides/webhooks)
-`;export{e as default};