feat: custom hashFn composable option

[johannschopplich]

🔗 Linked issue

Idea from #50

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSDoc annotations)
• 🐞 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)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

@killjoy1221 To ease the need for your composable overwriting the hashing logic, why not add an option to the composable itself? What do you think?
You could simplify your custom composable.

📝 Checklist

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

[netlify]

✅ Deploy Preview for nuxt-api-party ready!

Name	Link
🔨 Latest commit	47a37ca
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-api-party/deploys/650363da10759b000899aae5
😎 Deploy Preview	https://deploy-preview-51--nuxt-api-party.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mattmess1221]

What about also providing the key as a plain string the same way useAsyncData does?

useMyData("key", "path")

[johannschopplich]

That's probably the more native solution. 😃