Add utility methods to ctx, for example ctx.error that allow to show an error (ex. a parameter is required when used in combination with another) while staying in theme with the other errors. Maybe it could even then be used inside of the error_handler ext. to send the errors.

For reference:

• https://github.com/Pycord-Development/pycord/blob/master/examples/custom_context.py

ValueError: invalid literal for int() with base 10: 'list-8116'
gives this error when i tried to do avatar the last airbender and didnt add the : sign

Add classes and ev. methods to work with series seasons and episodes.

We could use redis in the bot for caching the api results and potentially various other things. However, integrating redis would mean everyone would need to have a redis instance available to be used when developing, or be forced to use docker. This may be a bit too complex for the contributors.

To avoid this complexity, @Paillat-dev has suggested using https://github.com/aio-libs/aiocache, which can just store the records into memory on it's own, without redis running on the side. This does indeed look very interesting, as it allows us to still have a cache service without the complexities involved with setting it up as a service running externally.

The aiocache library also supports actual redis integration, so it would even allows us to switch to redis eventually, if we would want it.

Unless it's deemed that cache really is needed though, we don't necessarily have to do anything.

We'll definitely need a database for the bot as we go on, we'll need to add support for it. Most likely, just using sqlite will be enough here and it will make it a lot easier for everyone involved when compared to having to work with a full dbms, like postgresql.

Question is whether or not we'll also want to do ORM (sqlalchemy) or just write some simple crud classes, or work directly with SQL everywhere. As much as I like sqlalchemy, it's probably a bit too involved and complex for us now. As for writing SQL directly, that could lead to issues and is probably more complex than just exposing some basic crud classes that everyone can use even without being familiar with SQL.

We already support showing details on movies / shows, but not on individual episodes.

• It would be nice if the embed that shows these details was paginated, so that people can scroll through the episodes.

Requires #34

When the search command is ran with some gibberish input, it fails with an unhandled exception.

Instead, it should show some custom error message for this occurence

Add a section to the readme above the installation guide, that explains what our bot actually does. This can include some demonstration screenshots / video captures.

While we don't have that many commands right now, this number will definitely grow and will likely result in the help embed being way too big (possibly even surpassing the maximum character limit for the embed). Because of that, we'll need to add support for pagination of the help command.

This should ideally be done with discord' interactive button components.

Sometimes, the error message shown by the error handler is not sufficient to figure out where an issue occurred. This is because it only shows the error class and the message. It would be nice to add a button that could modify the embed / send another embed / do something else to show the entire traceback to the user.

Alternatively, maybe this button could even directly open a github link with the body pre-filled to contain this exception (these links look like this: https://github.com/ItsDrike/code-jam-2024/issues/new?title=Issue%20Title&body=Issue%20Body) or maybe the traceback could get uploaded somewhere automatically and the error embed can just show some reference number under which we can find it.

If it doesn't clutter the embed, we could even include it directly, but I think in most cases the traceback is just way too big for that to look visually good in the error embed.

Currently, we only explore 1 level of subcommands and print whatever is in there, however, the subcommand might actually be another subgroup, which means we'll need some recursive logic there

There should be a command that allows the user to mark certain episodes as watched.

• We should support marking multiple episodes as watched at once, perhaps something like episode ranges i.e. (1-25 or s1e1-s3e4), since many people binge-watch episodes and adding one-by-one sounds like it could be annoying
• There should be a way to mark entire shows as watched, maybe also entire seasons, though that actually might be covered by the previous point.
• Consider supporting re-watches
• Track when the person saw given episode(s), maybe even allow people to change this.

Requires #22

This task requires basic TvDB support and database to be completed.

The /profile command should show the user's favorite shows / movies, amount of total shows added and whatever other things that come to mind.

Requires #22 #31

This is a low priority task for us, we can finish without having any unit-tests in place, however, it can provide a fun and useful task for someone if they can't find anything else to work on.

It would be very cool to be able to compare your profile with someone else's to find all of the shows / movies that you both seen, etc.

Idea by @Paillat-dev

Requires #27

Add an autocompletion feature using pycord's basic autocomplete.

For unload and reload, it should iterate over the bot's already loaded extensions. For load, it should use iglob or glob from the glob builtin to show all the available extensions in files.

Autocomplete, unlike choices does not enforce the autocompleted fields, which can still allow you to unput whatever you want, and that is nice

The LICENSE file should contain all of the contributors names and emails in the copyright / attribution section (just like those in pyproject.toml). Right now, it just says Python Discord, since that's a remnant from the original template repository owned by python discord.