Skip to content

Development Guide

Jump to bottom
Jedddy edited this page Jul 31, 2023 · 24 revisions

Setting Up

After Cloning or Forking

Go to your project terminal and type poetry install, (BUT make sure you have poetry installed or else it won't work. although).

Configurations

We have a configurations file named config.yml (DO NOT TOUCH THIS, this will be our production configurations). Since all developers have their own instance of the bot, you have to create your own config file at the root folder of our project. with the explicit name of user-config.yml and copy the configs inside config.yml then change the configurations to suit your bot instance.

Example, inside your user-config.yml file.

bot:
  prefix: "pph-"
  token: !ENV "token"

database:
  database:
  name: !ENV "db_name"
  host: !ENV "db_host"
  user: !ENV "db_user"
  password: !ENV "db_pass"

api:
  api_ninja: !ENV "api_ninja"

guild:
  staff_roles: [1063415177980170300] # make sure to change these to match your local development server
  dev_help_forum: 1083303587389648926
  log_channel: 1064597414440341575

Our configurations are loaded by startup. If you change any of your local configurations, you'd have to restart the bot. We have a config.py file where we load configurations into Python objects, for now it utilizes metaclasses (which is kind of overkill) but we can could change this to utilize pydantic-settings configuration loaders.

Note: Not all configurations are in config.yml. Some are saved inside the database (mostly the configurations that can be modified while the bot is running). You can use the handler in bot/database/config_auto.py to get/set configurations saved in the database.

Environment Variables

Create a .env file outside the bot folder. We have an .env.example file where you can check all the required environment variables.

│   .gitignore
│   config.yml
│   LICENSE.md
│   poetry.lock
│   pyproject.toml
│   README.md
│   .env  # <<< here
└───bot
    │   config.py

Database Migrations

We also have a migration library, yoyo. To migrate the database stuff to your local instance, just do yoyo init --database postgresql//your_database_uri migrations <- the migrations word here refers to the folder where the sql script files are. And then yoyo list, then yoyo apply.

Cogs

Inside bot/cogs/ folder, we will put our Cogs in there.

Ui

We will store all discord UIs in bot/ui/ folder.

  • views/ - All views in here
  • modals/ - All modals in here

Database

All database handlers are in bot/database/

Utilities

Main file

The only things we should put inside main.py are the things needed to setup the bot.

Styling

  • Follow PEP8 standard styling.
  • Always annotate your function parameters, and import the Class directly if ever ex:
from discord import Member, TextChannel, Interaction, ...
from discord.app_commands import command


@command()
async def test(self, interaction: Interaction, ...):
    ...

Documentations

Utility functions

decorators

We will put our decorator utility functions in here. You can refer to this if you want to make your own decorator.

Contents:


is_staff

A decorator for checking if the command invoker is a staff.

def is_staff():
    """
    Example:
        @is_staff()
        @command(description='Bans a member')
        @describe(member='the member to ban')
        async def ban(interaction: discord.Interaction, member: discord.Member):
            await interaction.response.send_message(f'Banned {member}')
    """
    def predicate(interaction: Interaction) -> bool:
        staff = False

        for id_ in Moderation.staff_roles:
            role = interaction.guild.get_role(id_) 

            if role in interaction.user.roles:
                staff = True
                break # Break the loop and continue the command if the invoker is a staff

        return staff
    return app_commands.check(predicate)
Clone this wiki locally