fix: allow pathParams to be reactive getter

[mattmess1221]

🔗 Linked issue

❓ 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

pathParams didn't support being passed via

const id = ref("0")
useApiData("endpoint/{id}", { 
  pathParams: { id }
})

📝 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	af864a6
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-api-party/deploys/64e9d06a6b4d9c0009039e1f
😎 Deploy Preview	https://deploy-preview-39--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.

[johannschopplich]

Thanks for the PR. I get your point. It is a valid one. But I intend do keep the reactive logic as close to Nuxt/VueUse as possible. For nested reactive assignments, a ref or getter function should be used. The latter one wasn't supported before, which will be fixed by this PR.

const id = ref(10)

const data = await $myApi('foo/{id}', {
  pathParams: () => ({
    id: id.value
  })
})

Although this syntax is more verbose, it aligns more with VueUse composables. I have added an example to the documentation and hope that's fine for your use-case.