We could use something like react-diagrams to represent all Listeners to (and maybe Emitters of) AppEvents in a visual way in the Operator.
The functions called on appEvents could be stored in the database and evaluated during runtime (This could be the trickiest part to get this done in a save way.)
New relations could be created from the Operator and reference these functions.
This could probably be expanded to include other things like shipping surcharges/restrictions calculation, product publications and so on.
We could use something like react-diagrams to represent all Listeners to (and maybe Emitters of) AppEvents in a visual way in the Operator.
The functions called on appEvents could be stored in the database and evaluated during runtime (This could be the trickiest part to get this done in a save way.)
New relations could be created from the Operator and reference these functions.
This could probably be expanded to include other things like shipping surcharges/restrictions calculation, product publications and so on.
What would you think of that idea?