Clean Up!
Before I accept contributions I need to standardize it more. For instance currently I am using arbitrary names.
This makes coding as a team harder since there is no docs you can rely on. You have to try it out and see what it returns. Then you can write your code around it. At some point I might change the name and it'll break your code.
This is why I wil…
Before I accept contributions I need to standardize it more. For instance currently I am using arbitrary names.
This makes coding as a team harder since there is no docs you can rely on. You have to try it out and see what it returns. Then you can write your code around it. At some point I might change the name and it'll break your code.
This is why I will transmit any object (message, guild, member, ... object) in a format as specified in Discord's Developer Portal's Documentation.
Secondly although I did write a lot about how to set it all up it can still be pretty confusing. Thus I plan on giving Docker support to ensure a quick and easy deployment so you can start developing.
I haven't created Docker images so far but I think it shouldn't be too hard.
Finally I want to create a demo front end so you can have a working example. This will not be aesthetically pleasing since I suck at front end. I'd rather have someone else do this.