Michaela Robosova

Hi @cizza, I'm sorry for the late reply, I've been busy lately. Thank you for your suggestion- sounds useful to me, too!

Hi, something like that is quite easy to add and might be useful, I've just labeled is as a feature request.

Hi, I checked some options and I don't think there is a simple way right now. You could add icons to all links with something like ``` .NavigationItem::before { font-family:...

Hi, thank you. > Why not provide generated id and **class** for every item in the tree and by adding them special prefix in in them so that it won't...

Ok, thanks. I'm planning to release v4 so this will be probably included. Didn't have much time through holidays but will be back open-sourcing since the second half of September.

I've decided to release v4.0.0 without this feature since 4.0.0 contains some updates which could be quite useful so I don't want to wait longer than needed for the new...

It's first item on my to-do list :) Contributions are welcome!

Hello, you can use `external` instead of relative `path`, this behaviour is described https://misrob.github.io/vue-tree-navigation/#/usage#items and there's an example here https://misrob.github.io/vue-tree-navigation/#/examples/manual When thinking about it, it might be better to call...

Oh yes, I get what you mean now. The library is currently built on working with the tree structure but I've been already thinking about adding support for route's config...

Sure, in what form would you like to do that? There're two ways: 1. Become a contributor (help is welcome!) - in that case we would need to discuss specification...