I wrote an #EmberJS2018 blog post about shifting the mental model for the framework! I think by changing the way we talk about and teach Ember, we can strip away the layers of "magic" and get more people involved and interestedhttps://medium.com/@pzuraq/emberjs-2018-ember-as-a-component-service-framework-2e49492734f1 …
-
-
yeah, I feel like the more you think of Ember as Component-Service, the more Controllers stick out as a hangover from the MVC days that we need to fix somehow. I think there's a lot we could do to improve them, or we could focus on replacing them entirely
-
If it weren’t for needing them for query params I don’t know that we’d use them for any new code at all. A top level component which receives the model from the route and injects any needed services usually does more of what we want with fewer surprises.
-
I think that "scoped services" make sense in some cases, but the singleton-ness is a real issue for that use case. QPs are probably the main reason they weren't deprecated years ago.
-
Would it be possible to make a query param service that could be injected into components? It'd probably derive a lot of info from the router service, but...could maybe be an alternative to controllers?
End of conversation
New conversation -
-
-
I've used https://github.com/kellyselden/ember-controller-lifecycle … to simulate this.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.