RFC - More modular way to write getStaticPaths/getStaticProps/getSSP

[Vadorequest]

PR: #346 and #347

Very basically, I've changed the way to write the 3 main functions for generating Next.js pages.

The new way allows for a more modular design and better reusability of the source code.

Before:

const getCoreLayoutStaticPaths: GetStaticPaths<CommonServerSideParams> = async (context: GetStaticPathsContext): Promise<StaticPathsOutput> => {
  // Implementation
}

After:

export const getCoreLayoutStaticPaths: GetCoreLayoutStaticPaths = (options?: GetCoreLayoutStaticPathsOptions) => {
  const {
    fallback = false,
  } = options || {};

  const getStaticPaths: GetStaticPaths<CommonServerSideParams> = async (context: GetStaticPathsContext): Promise<StaticPathsOutput> => {
  // Implementation
  };

  return getStaticPaths;
};

Now, the call site (usually, the page itself) has more power, it can re-use part of the logic while providing options to disable some behaviour.

// In some page
export const getStaticPaths: GetStaticPaths<CommonServerSideParams> = getDemoLayoutStaticPaths();

// In 404 page
export const getStaticProps: GetStaticProps<SSGPageProps, CommonServerSideParams> = getPublicLayoutStaticProps({ enable404Redirect: false });

Share your thoughts! 😄

[Vadorequest]

Yeah, I mixed the function names in the example.

[Vadorequest]

I fixed it, thanks!