docs: set correct default value for deep option in usefetch #32724
Conversation
This file contains hidden or 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
|
|
|
as with the other PR, the default is false for v4 what made you think otherwise? |
|
@danielroe I know, I made the misstake of adjusting it to v4 first, this is a change for v3 docs |
danielroe
approved these changes
Jul 22, 2025
|
thank you! |
Merged
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.
🔗 Linked issue
📚 Description
This pull request updates the documentation for the deep option in useFetch to set the default value to
trueinstead offalse. This change aligns the documentation with the actual implementation in the source code and ensures consistency for users referencing the docs.Motivation
Previously, there was a discrepancy between the Nuxt 3.x documentation and the codebase regarding the default value of the
deepoption. The documentation stated the default wasfalse, while the implementation and expected behavior is true. This update corrects the documentation, helping prevent user confusion and improving clarity.Summary of changes
true.