USER_JOINED webhooks are fired as NAME_CHANGE with empty type-field #1302
Labels
3rd party integration
Related to APIs for inbound/outbound interfacing with others.
chat
Issues dealing with the web chat client and server
Milestone
Hello,
while working on #1274 and #1016 and testing the webhooks I noticed that the USER_JOINED webhook is not sent when a user joins the chat. Instead a NAME_CHANGE webhook is fired, with an additional empty string field called
type
ineventData
.Sample webhook data when a user joins:
in contrast to a "standard" Name-Change event:
Expectation
I'd exepect the toplevel type to be "USER_JOINED" or at least the inner "type"-field to be "USER_JOINED". Not saying that this is not enough to differentiate between a USER_JOIN and USER_NAMECHANGE event, but I just think the way it is handled right now is not really intuitive for consumers of the Webhooks.
Reproduce
podman run --name owncast --network host docker.io/gabekangas/owncast:latest
(can use docker instead of podman)http://localhost:8080/
)Affected Version(s)
The text was updated successfully, but these errors were encountered: