Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Plugin discovery and activation? #7

Closed
3 tasks
arcivanov opened this issue Aug 25, 2023 · 2 comments
Closed
3 tasks

Plugin discovery and activation? #7

arcivanov opened this issue Aug 25, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@arcivanov
Copy link
Member

arcivanov commented Aug 25, 2023 •
edited
Loading

Currently the plugins are enumerated and activated statically.
There is a need to discover plugins dynamically.
Dynamic discovery of plugins raises the following concerns:

  • How to discover plugins: entry points or subclasses or both?
  • In what order to initialize the plugins that may be interdependent? Manual order, dependency tree etc?
  • Which of the discovered plugins to initialize? All discovered or manually specified? If manually specified where are they specified? Is a new Ktor initialization phase and/or file required?
@arcivanov arcivanov added the enhancement New feature or request label Aug 25, 2023
@arcivanov
Copy link
Member Author

@jemishp

@jemishp jemishp mentioned this issue Aug 31, 2023
Closed
@arcivanov
Copy link
Member Author

Fixed in #11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@arcivanov