search

Skellington-Closet / skellington

:sparkles::skull::sparkles: The skeleton for your bots
MIT License
64 stars 6 forks source link

Refactor #29

Closed colestrode closed 7 years ago

colestrode commented 7 years ago

It's about that time... maybe something like this?

lib/singleBot (sets up a single team bot) lib/slackApp (sets up a slack app) lib/config (manages config) lib/help (registers help listeners) lib/server (starts webserver, etc) lib/lifecycle (initializes plugins, botConnected)

colestrode commented 7 years ago

An interesting feature of skellington is the ability to run multiple instances in one process... it would be nice to not lose that. This probably means the skellington() function will need to manage it's config and pass it to subsequent modules.

colestrode commented 7 years ago

I kept with the proposed layout except for the config service. I left config formatting/validation as part of the main skellington file. It seemed to easy to accidentally store state in a config service :)

Closed as part of #30