feat(nuxt3): support custom prop for <nuxt-link>

[frbuceta]

🔗 Linked issue

nuxt/nuxt#13485

❓ 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

Resolvesnuxt/nuxt#13485

📝 Checklist

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

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	b4b2925
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/62c7178ad75ed600088a3f3a

[pi0]

Not sure about all possible context keys but shall we provide navigate (aliased to navigateTo) and rotue (lazy getter of useRoute) to be identicaL to vue-router API?

[frbuceta]

We can provide them with the help of useLink, and also rel and target

[pi0]

Nice idea but useLink implementation is not universal yet. We need to implement it here

[frbuceta]

Something like that? (last commit)

[pi0]

No, actually. Universal utils don't use vue-router dependency but mimic its API.

[danielroe]

Pushed some fixes. Only question remaining in my mind is whether we want to normalise the bound props passed to the default slot between external/internal links. (so would need to pass a route object to an external link, etc.) WDYT @pi0?

[pi0]

Only question remaining in my mind is whether we want to normalise the bound props passed to the default slot between external/internal links. (so would need to pass a route object to an external link, etc.) WDYT

How do you imagine extending vue-router's route type for external routes? In general, it wouldn't be a bad idea to me always providing a normalized route for external links as well.

[pi0]

Thanks <3