Route should have no awareness of what may or may not be rendered in its corresponding templating.
-
-
This is a completely quick, not fully thought through look at what it could look like:https://gist.github.com/thoov/985e5689058bee791874e88c16899c00 …
-
This is really cool! I’m probably being dense, but I still don’t see the advantage of the template invoking the component vs the data() hook passing args and invoking it directly. Removing the top template reduces concepts devs need to learn.
-
There's no reason you couldn't give the top component a class, but on the other hand what do you really need it for?
-
Better: make it have outer HTML semantics, same as Glimmer components, and that problem just goes away.
- End of conversation
New conversation -
-
When doing these tonight exercises in future, can we immediately move them to https://discuss.emberjs.com so they’re more easily discovered and contributed to?
-
I hereby declare that anyone inspired by these thought exercises should open a thread on discuss and link it in a tweet response. People having the thought exercises don't always know when they're striking on something new/interesting.
-
A 25 tweet thread is usually a good indicator
Just making people aware that’s all 
-
Did you guys just call "Bungo" on this thread?
-
Someone called for a rebrand for
#EmberJS2018 and I could get behind Bungo.js - 1 more reply
New conversation -
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.
If the route knows what data is being fetched, what’s the downside of it preparing the data shape for the template?
