search

Pierre-Demessence / Cornibot

A Discord bot
MIT License
2 stars 3 forks source link

Admin Interface #13

Open Pierre-Demessence opened 4 years ago

Pierre-Demessence commented 4 years ago
  1. Should be able to use the bot entirely without ever having to connect to the VPS where it's hosted, nor the database.
    • Need a system powerful enough to give the ability to change common config for every command (allowed roles, allowed channels, should the bot delete the command message, etc...) as well as command-specific config (RSS feed links, max amount of remind me per user, etc...).
  2. Could also be usable as a secondary tool to view data.
    • For example we should be able to see the list of mutes, see karma of people, etc... ⚠️ This should be secondary meaning it should always be possible to do it through the bot.
  3. Could also be usable as a secondary tool to interact with data.
    • For example we should be able to unmute people, answer to complaints/tickets, etc... ⚠️ This should be secondary meaning it should always be possible to do it through the bot.
Pierre-Demessence commented 3 years ago

For 1. it would be good if the system was automated. Commands/Services/Observers should have a Config object containing all the parameters. Each param should be typed with some specific types (you can't use arbitrary types the Config System doesn't understand). Client side, the config system should retrieve the list of params and create a form according to the type of each param. Bonus: Params can be annotated with more info like validations (min / max number), help text, etc...

Also all Commands should have a base Config with stuff shared by every

Example of types: