Wrapify restricts the decorator to methods defined within classes. There are no technical limitations as to why this isn't possible. However, Wrapify maintains the properties for each class independently, to avoid clashes in naming conventions and triggering multiple instances within the module. This is especially problematic since the publisher ports would clash with other triggering calls. We can resolve this issue by spawning a MiddlewareCommunicator for the module itself.
Wrapify restricts the decorator to methods defined within classes. There are no technical limitations as to why this isn't possible. However, Wrapify maintains the properties for each class independently, to avoid clashes in naming conventions and triggering multiple instances within the module. This is especially problematic since the publisher ports would clash with other triggering calls. We can resolve this issue by spawning a
MiddlewareCommunicatorfor the module itself.