By nesting routes, it enables you to easily maintain a parent-child relationship and ember.js pretty explicitly states that when you are creating routes that the child route is expected to be rendered into the parent template via an {{outlet}}. I agree that a fair majority of the time this is a good idea, but what about the cases where you want to display a model in its own template (within whatever parent you are rendering into) without displaying the parent? What if you are nested many levels deep? I feel that often this can lead to unnecessary clutter in your interface.
Your new post is loading...