-
Notifications
You must be signed in to change notification settings - Fork 769
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Proposal] Plugin system #5593
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Cadence provides multiple options/clients for components like:
Storage:
Document search:
Archival:
Having so many components built-in makes dependency version control complicated. Adding another component/client most likely will bring more dependencies to the code.
This also makes problematic to keep up with dependency versioning and introducing/experimenting with additional features will require approval from Cadence team.
Proposed Solution
I propose to implement a "plugin" system where you could declare external repository to be used.
Plugins interface can be declared to represent a concrete component in Cadence, for example:
One of possible implementation method: generate an entry
main.go
file where"import"
section would be generated based onplugins
you defined.This gives at least two benefits:
Additional context
Relates to #5584
The text was updated successfully, but these errors were encountered: