Mortar sample with Flow 1.0.0-alpha about mortar HOT 6 OPEN

Getting into the thick of this now, migrating a large app that leans very heavily on Mortar. Rather than migrate all of our Mortar provided services to Flow, I'm making MortarScopes the only service that Flow provides. Maybe eventually we'll bother to turn everything into a Flow service, maybe that won't be worth the effort.

Not thinking too hard yet about how I'd start from scratch. mortar.Scoped is pretty handy, and there is a useful kernel to mortar.Bundled. Perhaps the thing is to create new versions of them in Flow? Perhaps a new Mortar Lite library that builds on top of Flow?

from mortar.

More likely is a Flow integration module, but not until after Flow 1.0 beta.

from mortar.

@alexrwegener I'm implementing a sample project using both
If you may, check it out !
Contributions and feedback are pretty welcome !

from mortar.

It'd be great if there was some movement on this. Flow has changed a lot and it's not obvious how to integrate Mortar with it based on the samples. The samples seem all over the place, and are somewhat confusing. It'd be great if there was some movement on this to add clarity, and show that this project was still active.

from mortar.

Considering there is a service locator embedded inside Flow 1.0-alpha that is kept alive by Flow's KeyManager, it doesn't really make sense to use another service locator on top of it (Mortar).

from mortar.

from mortar.