Paul Rumkin
Paul Rumkin
@lega911 I will. But you're using al-include in your example. Let's focus on modular structure, easy of use and flexibility. And thus it should to use al-html to load subroutes.
There is an regex router with params and tail capturing: https://jsfiddle.net/rumkin/y6xLu1sm/
@dev-rke I'm talking about development of real application not a todo list or hello world. I added routing, i18n and custom directives which is required for real development. Still this...
I think it would be proper way to instantiate controllers with `new` always.
In this case the better way is to use alight.Controller. As I see Scope interface is changed in v0.14 and it is not backward compatible.
I think that controller could looks like that: ```javascript class Controller { constructor(scope, el, expr, env) { this.$scope = scope; this.$el = el; this.$env = env; this.$expr = expr; this.$init();...
And I think that scope should not be mixed in controller. I'd prefer to assign controller to `$this` scope's property.
What is direct-directives? How to define it?
Declarative interface is about to avoid ugly constructions like `alight.directives.ns = alight.directives.ns || {};` in modular applications.
And about namespaces itself. It very important to separate code into modules. Namespaces is the best trick to avoid conflicts. I have two different projects where I've realised `toDate` filters...