Fixed issue with retrigger events when events have multiple versions #244
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Problem/Feature
There was an issue with
twitch retrigger
where channel.follow didn't work due to its multiple versions. The wrong object type was being used when unmarshaling the JSON, which didn't throw an error but didn't fill in any data. This wasn't noticed because the only time that object is used for refiring the event is when grabbing the subscription version, but for subscriptions with only one version available the subscription version can be empty and it'll default to the only one available.Description of Changes:
twitch retrigger
doesn't work for channel.follow due to having multiple versionsChecklist