Referencing functions in plugin config about rejoice HOT 5 CLOSED

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?

from rejoice.

@lloydbenson Plugins may require more than just JSON to be configured,
example can be https://github.com/iceddev/hapi-strategy plugin that adds a strategies (it requires the validation function to be passed as apart of the strategy options)

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 rejoice, Unless i'm missing something, I think it's a hard limitation.

from rejoice.

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?

from rejoice.

Glue has some hooks (such prePlugins), rejoice hides them,
I'm also unable to register plugin programmatically (via my plugin defined in the manifest) because Hapi fails when registering a plugin via a plugin.

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 ;)

from rejoice.

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.

from rejoice.