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
There is a mismatch in the documentation. Although, it is an obvious, easy fix, if someone blindly copy-pastes the wrong example code, they might have hard time finding out what they did wrong.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
For people in the future who ends up here, @timneutkens said:
... Both methods are supported btw, you can provide a full url instead of the object. But we're only showing the object in the docs for now, so good catch 💯
So when you read this, probably either way is accepted, and you have a different issue.
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 30, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug report
Describe the bug
There is a mismatch in the documentation. Although, it is an obvious, easy fix, if someone blindly copy-pastes the wrong example code, they might have hard time finding out what they did wrong.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
The example below is right: https://github.com/zeit/next.js/blob/canary/docs/basic-features/data-fetching.md#the-paths-key-required
The example below is wrong: https://github.com/zeit/next.js/blob/canary/docs/basic-features/data-fetching.md#fallback-false
Expected behavior
The documentation should be consistent
Screenshots
System information
irrelevant
Additional context
I have created a PR, with a fix, would be delightful, if this gets merged 🎉: #10893
The text was updated successfully, but these errors were encountered: