docs: Fix typo in retro-compatibility flag value #2294
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ng retro-compatibility This PR corrects a typo in the documentation. The step to disable the retro-compatibility flag currently instructs setting v4CompatibilityMode to true. However, the correct value should be false to disable retro-compatibility and start using the new response format.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
|
Oh my, I can't believe we let that slip through and that nobody has complained about it yet 😅 |
pwizla
approved these changes
Nov 21, 2024
pwizla
added
source: Dev Docs
pwizla
added
the
temp: port to doc6
pwizla
removed
the
temp: port to doc6
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
This PR corrects a typo in the documentation.
The step to disable the retro-compatibility flag currently instructs setting v4CompatibilityMode to true. However, the correct value should be false to disable retro-compatibility and start using the new response format.
This PR updates the documentation to correctly state that disabling the retro-compatibility flag requires setting v4CompatibilityMode to false.
Why is it needed?
The current documentation contains incorrect information, which may lead to confusion or improper configuration by users. This fix ensures clarity and accuracy.
Related issue(s)/PR(s)
Let us know if this is related to any issue/pull request