EventSub tracking issue

[Nerixyz]

The EventSub implementation is very basic right now, but it needs to be ready in the near future (https://discuss.dev.twitch.com/t/legacy-pubsub-deprecation-and-shutdown-timeline/58043). A few tasks that need to be done at some point (feel free to update) and I can't keep them all in my head or in the TODO.md file.

twitch-eventsub-ws

• Default of json_transform should be snake_case since it will be used most #5911
• Automatically infer timestamp for std::chrono types (currently json_tag=AsISO8601) #5912
• Get rid of clang-tidy warnings in generated code (trivial moves and unnamed arguments) #5913
• The generated implementation code (.cpp) starts with an empty line #5909
• Parse inner data of mutually exclusive fields as sum types (std::variant or similar) or using inheritance. channel.moderate's Event is currently 3336 bytes large (81% of a page on most systems) #5917
• Add unit tests (we already have googletest in the repository) #5918
• Run pytest in CI #5919

Chatterino Integration

• The websocket connections need to die when user is changed #5926
• Should the client reconnect when the auth token is updated? #5929
• Check on behavior if PubSub is shut down (Do we get errors? Do reward messages come through? etc.) #5928
• Deserialize types in-place (as opposed to returning a result<T> and moving) #5927

PubSub Parity

• moderation.chatCleared
• moderation.messageCleared
• moderation.modeChanged
• moderation.moderationStateChanged
• moderation.raidStarted
• moderation.raidCanceled
• moderation.userBanned
• moderation.userUnbanned
• moderation.userWarned
• moderation.suspiciousMessageReceived
• moderation.suspiciousTreatmentUpdated
• moderation.autoModMessageCaught
• moderation.autoModMessageBlocked
• moderation.automodUserMessage
• moderation.automodInfoMessage

---

If you haven't done yet, please vote on "Allow getting realtime updates on polls/predictions/channel points redemptions through websockets for all users". We can't display reward information on channel point redemptions without PubSub. In EventSub, these subscriptions are hidden behind broadcaster authentication. There are ideas to work around that, but they require a dedicated server (RFC).

---

Some nice-to-have things:

• String could be 4 pointers large instead of 5 by using a custom SSO (i.e. union { QString, short-string, alloc'd string }) #5921
• Could we get rid of the .inc files? Either by manually writing the declarations for tag_invoke or by using a macro. #5922
• Avoid const in parsed values because it implicitly deletes move operations #5923
• Implement HTTP proxying for EventSub #5924
• Implement SOCKS5 proxying for EventSub (would require another dependency) #5925