Currently, auto_guild can only understand text and voice as channel types, but if a number was allowed, then existing configs can be used as templates. For instance, the following is what the production config for the pydis bot would look like:
categories:
information:
- welcome: text
In the proposed system, text can be a number: welcome: 123456789. Under the proposed system, any unrecognized number would default to text, which in the case of the python bot is just fine.
Alternatively, channels could be converted to objects like categories with a type and id key. This introduces more bloat, but makes it more feasible to use the config and template as one.
Currently, auto_guild can only understand
textandvoiceas channel types, but if a number was allowed, then existing configs can be used as templates. For instance, the following is what the production config for the pydis bot would look like:In the proposed system,
textcan be a number:welcome: 123456789. Under the proposed system, any unrecognized number would default totext, which in the case of the python bot is just fine.Alternatively, channels could be converted to objects like categories with a type and id key. This introduces more bloat, but makes it more feasible to use the config and template as one.