Files
directus/src/components
Rijk van Zanten b5d6fdefa2 Add date(time) interface (#499)
* Add localized-format util

* Add active prop to v-input

* Add strings for datetime interface

* Add overflow-scroll prop to v-menu

* Add close-on-content-click prop to v-select

* Add datetime interface

* Show display value synced with prop

* Sync value with prop

* Set lang after user hydration

* Add NL date-fns lang to test datetime

* Fix locale fetching in date-fns

* Dont stage value if year isnt fully filled out

* Localize date fns based on shared util

* Handle type, render type based display

* Don't use exact on v-list-item

* Pass type to interface on v-form
2020-04-29 10:00:22 -04:00
..
2020-04-24 18:48:05 -04:00
2020-04-24 18:52:27 -04:00
2020-04-24 18:52:27 -04:00
2020-04-22 13:19:20 -04:00
2020-04-29 10:00:22 -04:00
2020-04-24 18:52:27 -04:00
2020-04-24 20:12:51 -04:00
2020-04-29 10:00:22 -04:00
2020-04-06 15:25:58 -04:00
2020-04-29 10:00:22 -04:00
2020-04-29 10:00:22 -04:00
2020-04-22 11:46:45 -04:00
2020-04-24 18:52:27 -04:00
2020-04-29 10:00:22 -04:00
2020-04-24 18:52:27 -04:00
2020-04-27 14:09:40 -04:00
2020-04-24 18:52:27 -04:00
2020-02-05 15:07:20 -05:00
2020-04-24 18:23:59 -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.