Open zoltanka opened 1 month ago
The FwbSidebarItem.vue
component's link
prop type has been updated to accept either a string or an object with a name
property. This change enhances the flexibility of defining the link
values, allowing both simple and more dynamic route specifications.
File | Change Summary |
---|---|
src/components/FwbSidebar/... |
Updated the link prop to accept a string or an object with a name property. |
In the sidebar's glow, a path we bestow, Links now abound, in string or name's flow. With object aplenty, navigation grows, Seamlessly guiding wherever we go. 🚀
[!TIP]
AI model upgrade
## `gpt-4o` model for reviews and chat is now live OpenAI claims that this model is better at understanding and generating code than the previous models. Please join our [Discord Community](https://discord.com/invite/GsXnASn26c) to provide any feedback or to report any issues.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Name | Link |
---|---|
Latest commit | ef43286897562c88c06b87b0c62b1f1d9989420f |
Latest deploy log | https://app.netlify.com/sites/sensational-seahorse-8635f8/deploys/6685638f7e231700089abdb8 |
Deploy Preview | https://deploy-preview-299--sensational-seahorse-8635f8.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.
Now, what I made here is a very rudimentary solution. First I'd like some feedback if you would be open for such an enhancement. Then I make a more cleaner solution.
298
In order to make the
<FwbSidebarItem>
work with named router links, I propose the following.Now of course, the type
{ name: string }
could be extracted into aninterface
if you wish.Edit:
This could be adjusted to take route parameters in the
FwbSidebarItem
, so the input would not be just{ name: string }
instead{ name: string, params ?: {[key: string]: string|number} }
Of course the type for the
params
is more complex than this:{[key: string]: string|number}
.Summary by CodeRabbit