Closed danp3d closed 8 years ago
Thx @danp3d , great to know you found your way around it. So, as you're just using it wrong i will close this issue, ok? Also, a few days ago i started a slack channel for those using Studio and i would like to invite you to join us. Its also the best place to have a direct discussion on new features and roadmap... If you have interest: https://studiojs.herokuapp.com/
UPDATE: It's not broken. I was using it the wrong way. I was using it as:
instead of this:
Hi,
First of all, congrats on the work here. The framework is pretty cool.
To the issue: I'm using the Redis publisher, and found a problem on it. The middleware returned by the redis publisher contains a wrong signature.
But the 'use' function in Studio actually calls the middleware with two parameters - and Studio is the second.
It's a very simple fix. I'm including a patch. (Please note I haven't checked the other middleware functions, just the Publisher ones)
fix-middleware-signature.patch.zip
In the meantime, I'm using the following hack to get it working (I can't change the source code inside node_modules since it's actually an automated build using docker):
This is just to ensure that the options object will have a 'promise' property so the app can limp along.
Cheers