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
Based on #396 , plugin load order determines the order in which events are handled.
As a result, specifying a plugin via command line arguments vs via config file results in different executions, and may actually change the results or mask subtle plugin interaction bugs.
If possible, the order of plugin execution should be consistent.
Easy (hopefully viable) solution: after all plugins are loaded, sort them alphabetically by module name. That is their execution order.
The text was updated successfully, but these errors were encountered:
Agree this is a problem worth solving. Providing the user a way to specify plugin execution order for non-built in plugins might be nice too, but at least having consistent ordering is definitely better than the status quo.
Based on #396 , plugin load order determines the order in which events are handled.
As a result, specifying a plugin via command line arguments vs via config file results in different executions, and may actually change the results or mask subtle plugin interaction bugs.
If possible, the order of plugin execution should be consistent.
Easy (hopefully viable) solution: after all plugins are loaded, sort them alphabetically by module name. That is their execution order.
The text was updated successfully, but these errors were encountered: