At the moment, there are some private static final fields that are written in lower case, and others are upper case.
We should decide on either convention and update the whole code accordingly.

Another thing that should be factored into considerations: loggers, do we call them LOGGER, logger, log, or something else?

Please provide your opinions on what we should settle on!

Describe the bug
Right now, only the execution of the command itself is async.
However, loading the user settings, which is the longest part as it involves I/O, is happening in the ws thread. This could lead to discord timeouts in the future.

Expected behavior
The whole code in onCommandInteraction should be sent to the thread pool, not only the execution of the command itself.

This action will work by looking for code that has been taken without permission and that is not a fork

Is your feature request related to a problem? Please describe.
Instead of using System.out.println a logger should be used as this is a major bug and as said by Sonar lint

"If a program directly writes to the standard outputs, there is absolutely no way to comply with those requirements. That’s why defining and using a dedicated logger is highly recommended."

Describe the solution you'd like
Introduced a logger system and replace all the System.out.println

According to this changelog blogpost, the set-output command is deprecated and should be replaced. This affects the Build & Release workflow.

Rather than modifying the auto roles one by one, we should use select menus for that job since they're perfectly suited.

See https://discord.com/developers/docs/interactions/message-components#select-menus

GH Environments seem to be perfect for our plan to have a Production and a Beta Bot

I'll soon be working on improving the settings base which should make commands like setleavechannel obsolete. Please give suggestions on what you want to see being implemented!

Welcome messages could be abused by setting offensive / illegal messages, we should add an embed as a notice that clearly states that we don't have anything to do with the message sent and that we don't take any responsibility.

The warns system is currently really bad and only has very limited functionality, we should improve that.

BLOCKED until #168 is done

Release Notes: https://javalin.io/news/2022/04/09/javalin-4.5.0.RC0-released.html

Is your feature request related to a problem? Please describe.
I had situations where other people made polls but without adding any reactions or related. For that, I would add a message argument to the poll command so you can use an existing message

Describe the solution you'd like
Add a message option to the poll command, makes the content redundant, thus should probably be a subcommand

I will be migrating all the moderation commands to slash command. It might take some time like a week.

Using the todo-to-issue action, GitHub Actions could automatically open new issues for todos in the code. This would help to keep track of them without having to manually search through the code, and could be beneficial for newcomers to have a good overview of what they could help with.

Implement chat GPT

I am willing to add support for chatgpt and we can use for commands likes /ask or to make things faster like checking for things.

More tests would help make the base safer.

Checklist of whats left to implement:

• OAuth2
• API endpoints
  • paths
  • whoami (mocking)

Please add more ideas for tests, the more that's tested the safer it is!

Description

Basically, migrate all the @NotNull, @Nonnull, @Nullable and similar annotations to the javax version to remove duplicates.

Note

this should be tackled just before releasing the v2 (aka the slash command / recode version) so it's done once and for all

It is a pain to maintain and also forbidden by discord and google's ToS, and thus should be yeeted from the project.

Right now, the language is being parsed from a codeblock.

That's leftover from the pre-slash command era, and now that multiple options exist, we should make use of that by adding an option to specify the language of the pasted code.

Additionally, since slash commands only allow one-line freeform inputs, we should consider switching to modals.
They allow a length of up to 4000 characters with the paragraph text input style which should be sufficient for most code.
See https://discord.com/developers/docs/interactions/message-components#text-inputs-text-input-styles

Is your feature request related to a problem? Please describe.
Switch gradle to kotlin as it is more secure

Is your feature request related to a problem? Please describe.
As seen with introduction of the time out in discord you can only set only a certain amount of time when using the timeout feature on Discord meaning if we introduced a system were give the user the ability to set a custom amount(max is 28 days)

Giveaways are currently really poorly implemented, it would be good to possibly move them to Guilds to make them more modular and performant

The command right now is really terribly coded, we should re-do it with subcommands.