I'm in the process of developing a bot with a relatively large number of features, and I'm in need of a better and more organized structure to handle all the requests. I want to ensure that operations are separated, so I don't have to write everything in a single file.
I have attempted to implement architectures like the Command Pattern to manage the separation of concerns, but I encountered issues with dependency injection and sharing common methods across all classes. It seems that I might not be using the most suitable pattern for this case.
Could anyone suggest an appropriate structure or pattern that would help manage these operations more effectively?
I'm in the process of developing a bot with a relatively large number of features, and I'm in need of a better and more organized structure to handle all the requests. I want to ensure that operations are separated, so I don't have to write everything in a single file.
I have attempted to implement architectures like the Command Pattern to manage the separation of concerns, but I encountered issues with dependency injection and sharing common methods across all classes. It seems that I might not be using the most suitable pattern for this case.
Could anyone suggest an appropriate structure or pattern that would help manage these operations more effectively?