vsTerminus
commented
3 years ago So I agree with this as a goal for the library. It's something I've always wanted to do but can never seem to focus my time on reaching that goal.
Basically, this library does not meet the requirements for an API channel. Nor does it even meet the requirements for a CPAN release. Primary because of three things: Missing functionality, missing documentation, and missing test cases.
The Discord API server has an FAQ where they list the requirements for a library getting its own channel. You can find it here: https://gist.github.com/meew0/bbbbd5348967dee5f7e84c0cd58983fd
- It should support the entire documented API featureset (minus voice). (Fail)
- It should be usable by other people. This includes having a decent documentation (Fail)
And for CPAN, it must have a decent suite of unit tests. As far as I can tell we meet the rest of the requirements.
So if we want this on Discord-API it needs to have those items addressed. Maybe we should identify the missing functionality. I'm missing everything related to sharding, file uploading, and probably a bunch of other things that my own bot doesn't leverage.
Documentation isn't hard it's just time consuming. The hardest part will be the unit tests (particularly for the gateway) and getting it out on CPAN so it's not so hard to install anymore (To me this is more important than getting a channel in Discord-API).
Disinterpreter
I suggest to send a request to official Discord API server for adding text chat with this bot. https://discord.gg/discord-api
Yes, Perl is dead, but we have a right to discuss and maintain the thing that we love.