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
Last night I played around with the PHP plugin quite a bit and it wasn't working for me. So I spent some time getting to really know it, logging the steps and determined that the
"php.on('exit', function() {"...
was always occurring before
"php.stdout.on('data', function(data) {"
so my returned result was always blank.
I hot-fixed the plugin locally by instead setting the opts.content and calling "next()" inside of on.('data') instead on.('exit')
Not sure if this is a problem local to my computer or PHP. I believe my ruby plugin was doing the same thing, I didn't go back and test this on the rb plugin yet though. Either way, it probably exposes that the plugin isn't 100% foolproof so I wanted to do my due diligence and inform you.
Cheers.
The text was updated successfully, but these errors were encountered:
Last night I played around with the PHP plugin quite a bit and it wasn't working for me. So I spent some time getting to really know it, logging the steps and determined that the
"php.on('exit', function() {"...
was always occurring before
"php.stdout.on('data', function(data) {"
so my returned result was always blank.
I hot-fixed the plugin locally by instead setting the opts.content and calling "next()" inside of on.('data') instead on.('exit')
Not sure if this is a problem local to my computer or PHP. I believe my ruby plugin was doing the same thing, I didn't go back and test this on the rb plugin yet though. Either way, it probably exposes that the plugin isn't 100% foolproof so I wanted to do my due diligence and inform you.
Cheers.
The text was updated successfully, but these errors were encountered: