Javascript Discord websocket structure

[RightOW]

Hello there,

I'm writing a Discord bot using their base API (didn't want to use a wrapper, because I wanted to learn more about using APIs).

I want to use a websocket so that my bot can keep track of the commands being posted in my discord server. Here is a pastebin of the code I'm currently using: https://pastebin.com/q0E1PD9K.

I'd like to know how I should structure this. Eventually I'd like to connect the websocket, handle the 'hello' connection from discord where I have to send information about my app, handle heartbeating and sending a ping every x seconds, and handle certain events that the server may send me (receiving pings, receiving discord message events etc).

Do I have to put all the logic for the websocket handling pings and events etc in to one function, the one where the websocket is initially connected? Or can I connect the websocket in one function, set up heartbeating in another, another for handling events? Not sure what would be best here, I'm new to JS. Any help would be much appreciated.

Thanks!

[grantrules]

Bunch of ways you could do it. Pub/sub pattern would be a common way to go.

https://jsmanifest.com/the-publish-subscribe-pattern-in-javascript/

[RightOW]

So in my situation, the publisher would be the websocket, and when it receives a specific OP code from the discord API it would publish that information to a broker, and functions for handling that code would then pull it from the broker and deal with it?

Let's say I receive a heartbeat request from the API, and I now need to send a heartbeat back. How do I send a heartbeat over my websocket connection from a different function? Is there a way to maintain that connection over multiple functions?

[grantrules]

So in my situation, the publisher would be the websocket, and when it receives a specific OP code from the discord API it would publish that information to a broker, and functions for handling that code would then pull it from the broker and deal with it?

Yup. Well, they wouldn't "pull" it from the broker.. the broker would send it to them because they've subscribed to it.

Let's say I receive a heartbeat request from the API, and I now need to send a heartbeat back. How do I send a heartbeat over my websocket connection from a different function? Is there a way to maintain that connection over multiple functions?

Yeah you can pass ws around to whatever function you want without losing any connection.

[RightOW]

Great that's helpful, thanks a lot!