fix(nuxt): use undefined rather than null for data fetching defaults
#27294
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
|
|
|
|
pi0
reviewed
May 21, 2024
atinux
approved these changes
May 21, 2024
This was referenced May 21, 2024
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
resolves #26295
📚 Description
This updates the default value for error + data in
useFetchanduseAsyncData, as well as inuseError(). It updates both the types and the runtime value in a backwards compatible way, sofuture.compatibilityVersion: 4is respected.One note: previously the default value of
useAsyncDatawas inconsistent. It was initialised tonullbut cleared inclearNuxtDatatoundefined. This PR preserves the inconsistency for v3 compatibility mode.