4
Extensions emit C(R)UD actions
Source: directus/directus#22095 · opened by @Dominic-Marcelino
Summary
In order for other extensions to listen for extensions changes they should emit create update and delete actions like other collections.
Basic Example
_No response_
Motivation
Listen to extension changes and require an extension from another extension.
Detailed Design
Same as in other services
Requirements List
Must Have:
• Emit actions for create, update and delete events
Drawbacks
n/A
Alternatives
n/a
Adoption Strategy
n/a
Unresolved Questions
_No response_
In order for other extensions to listen for extensions changes they should emit create update and delete actions like other collections.
Basic Example
_No response_
Motivation
Listen to extension changes and require an extension from another extension.
Detailed Design
Same as in other services
Requirements List
Must Have:
• Emit actions for create, update and delete events
Drawbacks
n/A
Alternatives
n/a
Adoption Strategy
n/a
Unresolved Questions
_No response_
No pledges yet. Be the first to back this.
Comments
Similar requests
Add `emitter` to flow extensions
4 votes · 0 comments
Directus Extensions: Provide Settings-Option
6 votes · 0 comments
Access to e.g. getAccountabilityForRole and ItemsService in @directus/extensions-sdk
2 votes · 0 comments
Allow extensions to access the configured directus cache
27 votes · 0 comments
Flows - System collections not available CRUD operations
1 vote · 0 comments
No comments yet.