fix(nuxt)!: include request url and params in useFetch key

[danielroe]

🔗 Linked issue

resolves nuxt/nuxt#14493, resolves nuxt/nuxt#14499

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

A regression of #4955 - we were not using the URL as a key if it was provided. This PR uses the url as default key (including params and baseURL if provided).

There is still room for future improvement here via nuxt/nuxt#14583, for example, and I'll be following up with some more PRs targeting specific issues.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[netlify]

❌ Deploy Preview for nuxt3-docs failed.

Name	Link
🔨 Latest commit	4826776
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/6373c1550b37a0000827135a

[pi0]

Any update on this @danielroe ? Last time we discussed i think we decided to combination of auto key and hash.

[danielroe]

@pi0 Sure! Would you summarise what the issues are from your point of view, apart from hashing the url key?

[pi0]

Async data key to be {key||autokey}-{hash(input)}. Does it makes sense?

[danielroe]

How about instead: options.key || ((no functional options) ? hash(url + options) : autoKey)?

The reason is that any hash of input options is going to mismatch between server + client if any of those options are functions.

[pi0]

By hash i mean url+query only not all options.

seems good idea to allow entirely overriding with custom key 👍

[danielroe]

excellent

[examgoal]

The fetch options key not working anymore! I think it broke it, please check again

[manniL]

@examgoal Please create a new issue with reproduction ☺️