6
Directus Extensions: Provide Settings-Option
Source: directus/directus#25876 · opened by @Dominic-Marcelino
Summary In a lot of cases some small extensions could need some place where they can store some values, but doesn't need an own full table. For these cases I'd love to see a dedicated settings column within the directus_extensions table. Basic Example In our popular [field-actions]( extensions users can define some functionalities on field-level for the interface and the display. It'd be great, if there'd be a global config, which would allow users to define default settings. However id doesn't makes sense to introduce a new table + custom UI for such simple use-case Motivation Providing a unified settings-solution for small / simple extensions. Detailed Design 1. Devs define a settings-form comparable to the interface / display options 2. Directus creates an settings UI based on the configs and stores the result as JSON in a new field (e.g as a popup from the extensions-list or listed in the settings module) 3. The extensions settings are loaded int…
No pledges yet. Be the first to back this.
Comments
Similar requests
Allow extensions to access the configured directus cache
27 votes · 0 comments
Bundle custom i18n translations with extensions
21 votes · 0 comments
Access to e.g. getAccountabilityForRole and ItemsService in @directus/extensions-sdk
2 votes · 0 comments
Add `emitter` to flow extensions
4 votes · 0 comments
Ability to login to directus using access token of a configured provider.
2 votes · 0 comments
No comments yet.