-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
fix: use undefined
rather than null
for data fetching defaults
#1265
Conversation
12a5811
to
4dd914a
Compare
4dd914a
to
7bae15d
Compare
nuxt.options.experimental = ( | ||
await applyDefaults( | ||
{ future: NuxtConfigSchema.future, experimental: NuxtConfigSchema.experimental }, | ||
{ future: nuxt.options.future, experimental: nuxt.options.experimental } | ||
) | ||
).experimental |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We only want to use the default values for future and experimental.
I'm reluctant to merge this as I think it adds too much complexity to maintain. Rather, when we release Nuxt v4, perhaps we can simply directly update the default to the v4 version? |
I agree with the approach of directly updating the default to the v4 version! After trying it myself, I also thought it would be difficult. |
π Linked issue
#1263
Fixes: #1216
β Type of change
π Description
This updates the default values of
error
anddata
foruseFetch
,useAsyncData
anduseError
in as well as upstream.It is designed to be backwards compatible as well as upstream.
π Checklist