This module is getting a bit... all over the place. Some stuff in here should probably be in its own module entirely or not weirdly split off one that exists, e.g. CommandParser et al from zerobot.command. Enums in zerobot.common.enums should be grouped with their respective modules rather than in this odd bucket of miscellaneous enums.
Also rethink what/how we export things in __init__.py files or if we should do that at all; as it stands, there's a bit of an assortment from all different parts of ZeroBot mixed into zerobot.common, and while that is kind of the point, it does obfuscate a bit where things are coming from. Perhaps after reorganizing things it would be worthwhile to take a look at what features and protocols import the most and either export those in common or perhaps set up some tasteful __all__ declarations.
Further, it's a bit weird having both a zerobot.util and a zerobot.common.util. The original idea was that the former is for things that ZeroBot would use internally and the latter for feature/protocol modules. However, features/protocols have used both at this point and it seems too arbitrary to have two different "util" modules; there should just be one.
This module is getting a bit... all over the place. Some stuff in here should probably be in its own module entirely or not weirdly split off one that exists, e.g.
CommandParseret al fromzerobot.command. Enums inzerobot.common.enumsshould be grouped with their respective modules rather than in this odd bucket of miscellaneous enums.Also rethink what/how we export things in
__init__.pyfiles or if we should do that at all; as it stands, there's a bit of an assortment from all different parts of ZeroBot mixed intozerobot.common, and while that is kind of the point, it does obfuscate a bit where things are coming from. Perhaps after reorganizing things it would be worthwhile to take a look at what features and protocols import the most and either export those incommonor perhaps set up some tasteful__all__declarations.Further, it's a bit weird having both a
zerobot.utiland azerobot.common.util. The original idea was that the former is for things that ZeroBot would use internally and the latter for feature/protocol modules. However, features/protocols have used both at this point and it seems too arbitrary to have two different "util" modules; there should just be one.