-
Notifications
You must be signed in to change notification settings - Fork 14
Referencing functions in plugin config #16
Comments
I am not sure what you have in mind here. Rejoice is simply a CLI utility that uses the glue manifest to start up. Do you have a PR in mind? |
@lloydbenson Plugins may require more than just JSON to be configured, There must be a way to add extra plugins written in code and combine them to the overall plugin list passed to glue, otherwise any plugin that consumes functions to be configured cannot be used with |
The point of rejoice is to use just a simple json structure and having the cli use that. You don't obviously have to use rejoice, you can use glue directly and many people prefer that if they like to express it via code vs configuration. I think what you are saying here is that you want the glue manifest to be more expressive. Wouldn't that be a glue issue you'd want to address? Or am I still missing the point? |
Glue has some hooks (such prePlugins), rejoice hides them, To summarize: there is no way to hook plugins that requires function references when using rejoice. Feel free to close the issue if you guys never hit such a requirement ;) |
I think you can use glue if you want to do programmatic registering rather than rejoice. If we wanted to do something in rejoice, I'd like it to be represented as a JSON object as that is the major goal of this repo. I will close this up but if you have other thoughts on the subject let me know. |
Sometimes it's impossible to define all plugins via glue's manifest,
(i.e when a method should be referenced by the plugin options)
It could be nice if rejoice could support hooks where plugins can be registered programmatically, maybe by leveraging glue's
preConnections
/prePlugins
hooks.Thanks.
The text was updated successfully, but these errors were encountered: