title: Why does Vue router require an empty path child route to be named in order to render?
body: <p>I have a route setup where there's a parent with child routes, like this:</p>
  <pre><code>{
      //name: 'ProductComments',
      path: 'comments',
      children: [
          {
              name: 'ProductComments',
              path: '',
              component: ProductComments
          },
          {
              name: 'EditProductComment',
              path: ':commentId/edit',
              component: EditProductComment
          }
      ]
  }
  </code></pre>
  <p>With the above configuration, Vue Router will render my <code>ProductComments</code> component if I visit <code>/comments</code>.  However, if I comment the <code>name</code> out and uncomment it on the parent, it won't render the <code>ProductComments</code> component and will give me the warning:</p>
  <blockquote>
  <p>The route named &quot;ProductComments&quot; has a child without a name and an empty path. Using that name won't render the empty path child so you probably want to move the name to the child instead. If this is intentional, add a name to the child route to remove the warning.</p>
  </blockquote>
  <p>But why is this?  The child is always a more &quot;specific&quot; route, so why does giving it a name magically cause it to render, whereas giving the name to the parent stops it?</p>