You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been thinking about the current implementation of modules in Marionette and one thing about them strikes me as strange. To explain, let me start by examining a list of their properties:
They can soon be extended. This makes them similar to most of the objects in the Backbone-Marionette universe, such as Item Views
They have a start/stop state, and a series of initializers and finalizers associated with them. This makes them like Applications.
They can recursively be nested by calling Application.module and passing a period-separated string of names. This makes them...a bit odd?
The third item there really stands out to me. Maybe there's some good use-case for the recursive parent-child creation mechanism, but I can't think of any. Do you use it? If there are some good uses, then, well, that's fine. I wouldn't be surprised if I'm simply not creative enough to see the use.
But if not I would propose removing it entirely in the next big update to Marionette, for the sake of a more consistent, simpler framework.
The text was updated successfully, but these errors were encountered:
Yes, I use it extensively... our directory structure is mapped to the namespaces. So files in js/editor/sidebar/*.js are all in the Editor.Sidebar namespace.
I've been thinking about the current implementation of modules in Marionette and one thing about them strikes me as strange. To explain, let me start by examining a list of their properties:
Application.module
and passing a period-separated string of names. This makes them...a bit odd?The third item there really stands out to me. Maybe there's some good use-case for the recursive parent-child creation mechanism, but I can't think of any. Do you use it? If there are some good uses, then, well, that's fine. I wouldn't be surprised if I'm simply not creative enough to see the use.
But if not I would propose removing it entirely in the next big update to Marionette, for the sake of a more consistent, simpler framework.
The text was updated successfully, but these errors were encountered: