Breaking out /slash activities into it's own file
Breaking out /slash activities into it's own file
Hey guys, we are making heavy use of the @activites.slash decorator, something along the lines of:
But think duplicating that decorator 20 times for various commands. Any ideas/examples of how we can seprate this code out into a separate file and importing back into __main__? We are currently keeping everything inside of the __main__.py at the moment and it's getting messy because we have a lot of slash commands building up.
Also if we need to handle multiple slash scenarios is the best approach just continuing to duplicate the @activies.slash decorator over and over again?
Hey guys, we are making heavy use of the @activites.slash decorator, something along the lines of:
But think duplicating that decorator 20 times for various commands. Any ideas/examples of how we can seprate this code out into a separate file? We are currently keeping everything inside of the __main__.py class at the moment and it's getting messy.
Also if we need to handle multiple slash scenarios
#question
#bdk
#python
Breaking out /slash activities into it's own file
Breaking out /slash activities into it's own file
Hey guys, we are making heavy use of the @activites.slash decorator, something along the lines of:
But think duplicating that decorator 20 times for various commands. Any ideas/examples of how we can seprate this code out into a separate file? We are currently keeping everything inside of the __main__.py class at the moment and it's getting messy.
Also if we need to handle multiple slash scenarios
Hey guys, we are making heavy use of the @activites.slash decorator, something along the lines of:
But think duplicating that decorator 20 times for various commands. Any ideas/examples of how we can seprate this code out into a separate file? We are currently keeping everything inside of the __main__.py class at the moment and it's getting messy.
#question
Breaking out /slash activities into it's own file
Breaking out /slash activities into it's own file
Hey guys, we are making heavy use of the @activites.slash decorator, something along the lines of:
But think duplicating that decorator 20 times for various commands. Any ideas/examples of how we can seprate this code out into a separate file? We are currently keeping everything inside of the __main__.py class at the moment and it's getting messy.
Hey guys, we are making heavy use of the @activites.slash decorator, something along the lines of:
But x 100. Any ideas/examples of how we can seprate this code out into a separate file? We are currently keeping everything inside of the __main__.py class at the moment and it's getting messy.
#question
Breaking out /slash activities into it's own file
Hey guys, we are making heavy use of the @activites.slash decorator, something along the lines of:
But x 100. Any ideas/examples of how we can seprate this code out into a separate file? We are currently keeping everything inside of the __main__.py class at the moment and it's getting messy.