You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An application can only determine if you're in Preview Mode via getServerSideProps or getStaticProps.
This can lead to noisy prop drilling to render preview states in different parts of your application, and make it difficult to render something specific to preview mode in Custom <App> due to the lack of dedicated getServerSideProps or getStaticProps for that file.
Describe the solution you'd like
Next.js' router should provide preview state, similar to fallback state:
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 28, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature request
An application can only determine if you're in Preview Mode via
getServerSideProps
orgetStaticProps
.This can lead to noisy prop drilling to render preview states in different parts of your application, and make it difficult to render something specific to preview mode in Custom
<App>
due to the lack of dedicatedgetServerSideProps
orgetStaticProps
for that file.Describe the solution you'd like
Next.js' router should provide preview state, similar to fallback state:
We might also want the following to work:
This is an API idea, we're not entirely sure if we want to implement this yet. Just braindumping here!
The text was updated successfully, but these errors were encountered: