Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: cache initial data #388

Closed
wants to merge 1 commit into from
Closed

fix: cache initial data #388

wants to merge 1 commit into from
+5 −1

Commits on May 29, 2020

  1. fix: cache initial data 

    It appears some time ago the `initialData` configuration was used as a fallback.  When vercel#211 was merged, this behavior changed to be used with SSR like in the next.js example in the README.  Issue vercel#230 explains this was the expectation. I'm using SSR, so im fine with the new behavior.

Since `initialData` is now not quickly revalidated, another issue (vercel#308) has been raised.  Since `initialData` is not cached, and the mutate w/ callback grabs the curerent data from the cache, when `initialData` is used, `undefined` is returned.

fixes vercel#308
    @aj-may
    aj-may committed May 29, 2020
    Configuration menu
    Copy the full SHA
    16889bf View commit details
    Browse the repository at this point in the history