It now parses result as evalBulk does. Actually, the only difference between EVAL and EVALSHA should be that EVAL receives a script and EVALSHA receives SHA of the script, but it should behave the same and parse the received data the same way.
I wrote a new function evalSHABulk to avoid breaking anyone's code.
It now parses result as evalBulk does. Actually, the only difference between EVAL and EVALSHA should be that EVAL receives a script and EVALSHA receives SHA of the script, but it should behave the same and parse the received data the same way.
I wrote a new function evalSHABulk to avoid breaking anyone's code.