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.

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

Document the need to call App.getInitialProps() from a custom app's getInitialProps #24002

Merged
merged 1 commit into from
Apr 16, 2021

Conversation

marcvangend
Copy link
Contributor

This PR explicitly documents the need to call App.getInitialProps() from a custom app's getInitialProps. See #23055.

I'm committing this from the Github editor, so I did not check if linting passes (although it seems trivial for such a small change).

Documentation / Examples

  • Make sure the linting passes

Document the need to call App.getInitialProps() from a custom app's getInitialProps. See vercel#23055.
@timneutkens
Copy link
Member

Thanks!

@timneutkens timneutkens merged commit b7a1265 into vercel:canary Apr 16, 2021
SokratisVidros pushed a commit to SokratisVidros/next.js that referenced this pull request Apr 20, 2021
…etInitialProps (vercel#24002)

Document the need to call App.getInitialProps() from a custom app's getInitialProps. See vercel#23055.
@vercel vercel locked as resolved and limited conversation to collaborators Jan 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants