Builder Cacheing Issues?

Technical Questions
21

Hello @spm922,

Can you try add ing a key prop to the builder.get() call to make sure the response is differentiated which might help prevent any consolidation or caching of the content?

22

This doesn’t make a difference in my testing. Here is a sample of my get request

const page =
    (await builder
      .get("page", {
        userAttributes: {
          urlPath: "/" + (params?.page?.join("/") || ""),
        },
        key: params?.page?.join("/") || ""
      })
      .toPromise()) || null;
23

Hello @spm922,

We’ve made an attempt to reproduce this error on our end, but regrettably, we couldn’t replicate the issue. It seems there might be an issue with the next router, as the URL updates but the page content doesn’t refresh. Have you tried console.log the builder.get response to see if the page data is being returned correctly?

To delve deeper into this and provide you with the best assistance, could you please raise a ticket by reaching out to support@builder.io? Additionally, sharing access credentials for staging would be greatly appreciated.

Thank you in advance!

24

Thanks so much! The builder.get is returning the correct data however the builder component wasn’t refreshing on navigation using next/link. I added this key prop which seems to address the issue

<BuilderComponent model="page" content={page} options={{ includeRefs: true }} key={router.asPath}/>