Dynamic Routing Enhancements

[thescientist13]

Merge getStaticPaths / getStaticProps

Somewhat related, but I observed in Astro, that paths and props can be returned in the getStaticPaths function. Seems more convenient, something we should consider?

export async function getStaticPaths() {
  const response = await fetch('...');
  const data = await response.json();

  return data.map((post) => {
    return {
      params: { id: post.id },
      props: { post },
    };
  });
}

Dynamic Routing + getStaticPath + Content Collections

Coming out of #1675, I was wondering if static paths should be pushed to the graph? Then they could be used in content collections? (would have to figure out how to surface frontmatter meta data though, but even something like Astro just has you make ad-hoc collections (like with our Source Plugin)
https://docs.astro.build/en/guides/content-collections/#building-for-static-output-default

import { getCollection, render } from 'astro:content';

export async function getStaticPaths() {
  const posts = await getCollection('blog');

  return posts.map(post => ({
    params: { id: post.id },
    props: { post },
  }));
}

Source Plugin

Now that we have dynamic routing, do we still need the Source Plugin? I suppose as mentioned above regarding getStaticPaths + content collections, we would still need it.

Also, could be useful for folks that don't like file-based routing.