The big TODO list
See original GitHub issueSo @Emzi0767 gave me some ideas for future versions of the library. These ideas should further improve the library in a lot of ways. I’m excited!
Here’s a “little” checklist:
- Incoming voice
- Organize class members so that they are not all over the place, but are ordered according to some key. No effect on end-users, and will make maintenance easier.
- Make all entities immutable, and perform mutation via events only. This is potentially mildly breaking, but it will also eliminate some weird cases.
- Implement a message cache.
- Abstract data structures. This will make maintenance infinitely easier. No effect on end-users.
- Port VoiceNext to 2.x
-
.SetMute
and.SetDeaf
methods for DiscordMembers - Multi file uploading (to one message ofc)
- Settle on argument naming. I’m in favour of snake_case. Shouldn’t affect compatiblity.
- Setting on private field naming. Ditto as above.
- Rename all awaitable methods to
...Async()
. This could be potentially breaking, but it’d help reduce confusion by making it clear what needs to be awaited and what doesn’t. - Split the websocket and REST parts of the client for API communication. No effect on end-user, but will make classes smaller and easier to maintain.
- make
DiscordMember
inherit fromDiscordUser
rather than wrap it. This is going to make working with members infinitely easier. - Docs overhaul
- Command overhaul
- More example bots
- Support for different .NET versions, including .NET core
- Discord character limits
- Fix caches
- Sharding support
- Autosharding support
As emzi stated, the lib has grown quite a bit, and its code organization is messy.
If any of you have any other ideas, leave them as comments. Also: if anything listed gets implemented, also leave a comment so i can edit the main message.
Thank you
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:22 (19 by maintainers)
Top Results From Across the Web
I Tried 4 To-Do List Methods. Here's What Worked.
Once you have all three lists, start with list #2. Schedule the tasks you need to get done today on your calendar (similar...
Read more >The Big To-Do List - Dreaming Big. Burning Dinner. Raising ...
So, What Happened in 2021? 2021 year recap. Here's the obligatory year recap post for 2021! Hike-in camping, business updates, elephant tusks and ......
Read more >15 Secrets to Make a To-Do List That Actually Works
1. Capture everything · 2. Lists, lists, and more lists · 3. Organize your to-do list by workflow, priority, or due date ·...
Read more >To-Do Lists - The Key to Efficiency
Learn how to use a Prioritized To-Do List to manage tasks effectively. Our free template will help you get everything done, in the...
Read more >Try These 10 Simple Tips for Better To-Do Lists
1. Choose the Right App...or Paper · 2. Make More Than One List · 3. Write Down Your Tasks as Soon as You...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Maybe .Net Core support? (netstandard)
Since I don’t have any better place to say this and I don’t feel like creating another issue for it, I’d just want to say big thank to all of you guys for making this library work perfectly with my Mono setup ❤️. I hope I didn’t clutter todo list issue too much with this message, please keep being awesome! 🎉