Sent whisper returns emote-sets instead of emotes object

[scsddeputy]

Actual behaviour:
When sending a whisper the userstate object is different from receiving a whisper. On Received whisper the emotes are an object of the sets, but on a sent whisper the emotes are a string of emote sets

Sending Whisper:

{
    'badges': null,
    'color': '#FFFFFF',
    'display-name': 'Schmoopiie',
    'emote-sets': "0,123,324,3242",
    'message-id': '123',
    'thread-id': '1234567_12345678',
    'turbo': true,
    'user-id': '58355428',
    'user-type': null,
    'badges-raw': null,
    'emotes-raw': '25:0-4',
    'username': 'schmoopiie',
    'message-type': 'whisper'
}

Expected behaviour:

Received Whisper

{
    'badges': null,
    'color': '#FFFFFF',
    'display-name': 'Schmoopiie',
    'emotes': { '25': [ '0-4' ] },
    'message-id': '123',
    'thread-id': '1234567_12345678',
    'turbo': true,
    'user-id': '58355428',
    'user-type': null,
    'badges-raw': null,
    'emotes-raw': '25:0-4',
    'username': 'schmoopiie',
    'message-type': 'whisper'
}

Server configuration

• Operating system: Windows10
• Node version (if applicable): 6.9.1
• NPM version (if applicable):3.10.8
• tmi.js version:1.1.1

[AlcaDesign]

The whisper command merges the this.globaluserstate into the new userstate to be emitted when sending a whisper, hence the emote-set key (reference). It's not set to parse the emotes in the whisper command like the say command does by sending it through client._sendMessage (reference). You can load the parser file using require('tmi.js/lib/parser') (reference) if you're like to make use of it until this is fixed (if it hasn't been already).

[Schmoopiie]

AFAIK, Twitch is still not sending information when you are sending a message. This is the reason why we chose to merge, as @AlcaDesign said, the globaluserstate and a few information such as the username and message-type. I am willing to find a workaround for this but only in v2.0.0.