You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The use case is:
You have multiple plugins. But some of them may be expensive to execute, so you only want to use them as fallback.
Currently all plugins are executed, even though one plugin has already been successful and there is no need to execute (and waste any time) by calling another plugin.
So I think there should be an option the allows me to prevent the execution of further plugins after the first successful plugin.
The text was updated successfully, but these errors were encountered:
I'd be willing to review / merge a PR which implemented such a feature. Off the top of my head, I believe that it should be implemented as a plugin (or more than one) implementing the same interface as the "expensive" ones: it would be configured with a list of the "real" plugins for that interface, and would be the only one registered directly for it.
The use case is:
You have multiple plugins. But some of them may be expensive to execute, so you only want to use them as fallback.
Currently all plugins are executed, even though one plugin has already been successful and there is no need to execute (and waste any time) by calling another plugin.
So I think there should be an option the allows me to prevent the execution of further plugins after the first successful plugin.
The text was updated successfully, but these errors were encountered: