actions applied to app/configurable

[faassen]

There are a few cases where it is useful to have access to the app or configurable in an action. Normally I'd like to avoid it though. Would it be possible to have a special config variable that if named
'app' will pass it in (but not create it)?

[faassen]

And in some cases (like template directory ordering in Morepath) you want the app class where it was defined instead of the app class where it was applied.

[faassen]

When you stuff methods onto the app class (like with link_prefix) you also want the app class where it was defined, not the app class where it was applied. This way normal inheritance rules can be respected.

[faassen]

Okay, the last comment was wrong. If we register on a method of the app class (which Reg may require), we need the app class on which the directive is applied, as registrations are not inherited at all, just like they're not inherited by lookups now. Morepath only makes it seem like registrations are inherited by reapplying them to the subclass.

[faassen]

If we want the configurable where the directive was defined, we currently have to use this on the action: self.directive.configurable.