Files
directus/src/components
Rijk van Zanten 0347426e12 Interface single file (#605)
* Start on file interface

* Add preview icon

* Add readable mimetypes to extension

* Add file interface strings

* Fix type errors

* Add file select / deselect

* Add new file upload support

* Add import from url

* Fix loading state of url import

* Add filename in download attribute

* Replace option names with replace when file exists

* Remove / fix outdated tests
2020-05-21 16:47:01 -04:00
..
2020-05-20 16:38:31 -04:00
2020-05-08 15:33:54 -04:00
2020-05-15 18:44:21 -04:00
2020-04-24 18:52:27 -04:00
2020-05-15 18:44:21 -04:00
2020-05-13 19:31:30 -04:00
2020-05-13 14:06:14 -04:00
2020-05-12 20:10:48 -04:00
2020-05-15 18:44:21 -04:00
2020-05-19 18:02:04 -04:00
2020-05-15 18:44:21 -04:00
2020-05-15 18:44:21 -04:00
2020-05-21 16:47:01 -04:00
2020-05-20 16:38:31 -04:00
2020-05-15 18:44:21 -04:00
2020-05-19 18:02:04 -04:00
2020-05-12 20:10:48 -04:00
2020-05-15 18:44:21 -04:00
2020-05-12 20:10:48 -04:00
2020-04-24 18:52:27 -04:00
2020-05-15 18:44:21 -04:00
2020-05-15 18:44:21 -04:00
2020-05-15 18:44:21 -04:00
2020-05-15 18:44:21 -04:00
2020-04-30 17:01:14 -04:00
2020-02-05 15:07:20 -05:00
2020-05-20 16:38:31 -04:00

Components

Components are custom elements that can reused in various other places.

Storybook / Tests

Every component should have an entry in Storybook, and should have unit tests where appropriate.

Naming

Components must always have a - in the name. This makes sure we don't run into any conflicts with HTML element names.

Base Components

The core-most base-components are prefixed with v- (for example v-icon and v-button). These components can not rely on any global store.

Private Components

Every now and again, it makes sense to split up a bigger component in smaller sub-parts for code maintainability and organization reasons. These "internal private components" are prefixed with a _ and should never be used standalone.