Adam Soffer

Not sure. The page config might override it.

@aboveyunhai feel free to submit a PR if that fixes something not working. If persistent layout is what you're after check this out https://adamwathan.me/2019/10/17/persistent-layout-patterns-in-nextjs/

Hey @Xetera - yeah I wish dynamic/persistent layouts had first-class support in next.js. There is a workaround though; check out this guide by Adam Wathan 👉 https://adamwathan.me/2019/10/17/persistent-layout-patterns-in-nextjs/

Hey Lydia - yeah that's correct. You'll have to copy one of the solutions in that thread. Take a look at [this boilerplate](https://github.com/TheRusskiy/next-apollo-ts). Might look into updating this package to...

@chrbala - yeah pretty much! That would be awesome

Hey @chrbala - options 3 sounds good and the PR looks good! I'll try and cut a release this weekend. Thanks so much for this.

Cool thanks. Question I just thought of. Consider this scenario using option 3: 1. A user lands on a page that that does not use `getStaticApolloProps`. The page fetches data...

Gotcha. Thanks for the explaination! I think it's actually fairly common for apps to use `getStaticProps` on some pages but not others so we'll want to account for this. For...

hm cache seems to work fine on page transitions on [next-apollo-ts](https://github.com/TheRusskiy/next-apollo-ts). Is this necessary?

Gotcha. Sorry for dropping off. So I'm using next-apollo-ts on one of my projects and for some reason, the cache works as expected when navigating between a page rendered using...