Keg.init() having parameters breaks the "init() contract"

[rsyring]

The whole point of having an init() is to have a method that is safe to override without having to worry about passing parameters up the stack or call super().

The whole point of having the init() happen separate from the app setup was to facilitate being able to use the app as a decorator. When using a factory setup method, you can't get at the app instance to use it as a decorator, but Flask requires the app instance to use as a decorator. So when the app gets bigger and you want to move some of your stuff around, the app setup just gets ugly IMO.

Options:

• make the class object itself have whatever methods on it we need to decorate things and then just save them for assignment to the app instance once it's created.
• rename init() to something else like start()
• maybe the init name isn't so helpful and we should have a "on_ready() contract" where the name would be more indicative of what we really are trying to accomplish.

[rsyring]

I wonder if we could tie all the signals into the Keg app class automatically so that if a method exists on the app with the same name as a signal, it doesn't need to be explicitly wired.