getStaticPaths() suggested usage

[zackolsonHS]

I don't see any mention of how to utilize client with Next.js's getStaticPaths(). Currently attempting this with client.client.query.{schemaFunction}() based on autocomplete when drilling down through exported client that faust generates. When trying to utilize the generated client to make queries (since I cannot use hooks server side), the terminal is reporting that "no data requested" and values returned are undefined. This results in me being unable to pre-build pages dynamically, which is a feature I'd like to not lose with the migration from @wpengine/headless to @faustJS.

Are there any solutions or documentation on how to best perform a query within getStaticPaths() with Faust?

[zackolsonHS]

For those that may come to this and are wondering what resolved this issue, here was my solution.

When issuing GQTY queries from within getStaticPaths(), both client.client.resolved() and client.client.inlineResolved() were returning with a proxy yielding undefined data. Just returning the query we wanted (ie. client.client.query.generalSettings) was not sufficient to then access such values outside of the inlineResolved() callback. To get non-undefined data, you need to specify what fields you want to pull in within the inlineResolved() callback using one of GQTY's core helper functions. We used getArrayFields() as that was more appropriate for the use case within getStaticPaths().

Example snippet:

import { client } from "client";
import { getArrayFields } from "gqty";

// ...

export async function getStaticPaths() {
  const people = await client.client.inlineResolved(() => {
    return getArrayFields(
      client.client.query.people()?.nodes,  // used arbitrary query for people()
      "slug" // pull whatever field(s) you need
    );
  });
  const peopleSlugs = people.map((person) => {
    return {
      params: {
        person: person.slug,
      },
    };
  });
  // ...
  return {
    paths: peopleSlugs,
    // ...
  };
}