api.getPage() ignores some options on production

[mattcoy-arcticleaf]

When specifying options for a getPage request, such as limit, you are able to see the expected results on localhost. However, when the theme is bundled and pushed to the live store, the options no longer work (they are overridden by options set in the front matter for the page).

For example, if I run the following function in localhost, it will return 100 products, but on the live site, it will return the number of products specified in the category.html YAML:

There is a more thorough explanation written here (not by me): https://support.bigcommerce.com/s/question/0D51B00003sQyL1/stencilutils-api-getpage-options-issue

Any chance this can be fixed so we can specify options within our requests that differ from those specified in the front matter?

[mattcoy-arcticleaf]

@junedkazi , Any idea if this can be resolved? We have a store where we need these options to work.

[bookernath]

@mattcoy-arcticleaf we're not sure if this has ever worked in production, it might be an area where CLI can do something that our production server won't do.

I'm curious about the use case though - is the GraphQL Storefront API a better option for fetching data for 100 products, perhaps?

You might use a query like

  site {
    route(path: "/shop-all") { //category URL
      node {
        ... on Category {
          products(first: 50) {
            pageInfo {
              hasNextPage
              startCursor
              endCursor
            }
            edges {
              node {
                name //any product fields you need
              }
            }
          }
        }
      }
    }
  }
}

[mattcoy-arcticleaf]

@bookernath , sorry for the confusion. I was posting the products as a quick and concise example. My exact use case that I am trying to get working here is to get blog posts, which cannot be accessed by GraphQL.

[bookernath]

Gotcha, thanks for the extra context. We're looking into this more today.