Replaces the semistandard linting with a more general eslint configuration. This also includes Typescript specific rules.
Move to PostgreSQL
The game moved almost a year ago, and keeping a MariaDB server running just for this bot seems like a waste of resources.
Other changes
Make the custom logger use different console.* functions for each log level.
Make !coordinates actually work (bind the execute function to the command).
Adds a vscode launch configuration.
Breaking changes
Because of the move to PostgreSQL, you'll need to setup the bot with that database. mysqldump and pg_dump is your friend here, although them interacting correctly is not guaranteed. Check the changes on this PR and try to implement them into the dumped MariaDB
This PR also modifies the config table by dropping the id column and making guild_id the primary key, I thought the id column was redundant because guild_id was also marked as an unique key.
This PR brings a lot of updates to the codebase as a base for planned future changes.
Updates dependencies to their latest versions.
Most importantly, Typescript is now on v4, and Discord.js is now on v12. Both have some breaking changes.
Add linting
Replaces the semistandard linting with a more general eslint configuration. This also includes Typescript specific rules.
Move to PostgreSQL
The game moved almost a year ago, and keeping a MariaDB server running just for this bot seems like a waste of resources.
Other changes
console.*functions for each log level.Breaking changes
Because of the move to PostgreSQL, you'll need to setup the bot with that database.
mysqldumpandpg_dumpis your friend here, although them interacting correctly is not guaranteed. Check the changes on this PR and try to implement them into the dumped MariaDBThis PR also modifies the
configtable by dropping the id column and making guild_id the primary key, I thought the id column was redundant because guild_id was also marked as an unique key.