-
Notifications
You must be signed in to change notification settings - Fork 26
Feature: Update nodecg-io-streamelements to include test events #287
Feature: Update nodecg-io-streamelements to include test events #287
Conversation
Also yes, we require a 2.x.x version of the socket-io-client because streamelements hasn't updated their service and v3+ doesn't work with 2.x.x connections |
Dang 🤦. How many times did I accidentially upgrade the socket.io lib to 3.0.0 or higher? Propably too often, lol. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks in advance for this useful PR!
} | ||
}, | ||
"required": ["jwtToken"] | ||
"required": ["jwtToken", "handleTestEvents"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better if handleTestEvents
defaults to false
instead of requiring it here
@@ -1,6 +1,6 @@ | |||
{ | |||
"name": "streamelements-events", | |||
"version": "0.2.0", | |||
"version": "0.2.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really mind having 0.2.1
here, but 0.2.0
wasn't released yet and it would be kinda weird if we start with 0.2.1
when we're going to release 0.2
sometimes in the future. I think I'm gonna push some features of the 0.2 milestone into 0.3 so we can release all the new services.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
This PR adds a new field
handleTestEvents
to the SE config which controls whether it should also fire test events.Also bumps the version to
0.2.1
for the sample and nodecg-io-streamelements