fix: cannot resolve localePath correctly

[kazupon]

🔗 Linked issue

resolve #2523
resolve #2525

❓ 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

This issues is fixed via vue-i18n-routing

📝 Checklist

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

[kazupon]

@BobbieGoede
Can you add tests for cases #2523 and #2525 for regression? 🙏

[kazupon]

You can push fix/bump-deps branch.

[BobbieGoede]

@BobbieGoede Can you add tests for cases #2523 and #2525 for regression? 🙏

Added the regression tests.

For #2523 I had to guess the intended usage as there was no minimal reproduction.. The example given in the issue description would not have worked, so I made the assumption that the following changes would have been the intended usage.

const { localePath } = useLocalePath();
-const url = localePath('path/as a test')`
+const url = localePath(`/path/${encodeURI('as a test')}`)

Let me know if this should be different!

[kazupon]

@BobbieGoede
Thanks for your testing!