Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap? #8

Open
rubjo opened this issue Apr 6, 2022 · 1 comment
Open

Roadmap? #8

rubjo opened this issue Apr 6, 2022 · 1 comment

Comments

@rubjo
Copy link

rubjo commented Apr 6, 2022

Hi!

Thanks for starting this awesome project! I did a bit of research on what's available when it comes to command palette-type things suited for development with Vue.

This came up, along with a very few other projects (notably https://github.com/ssleptsov/ninja-keys, which seems nice, but is probably less extensive than kbar).

Before going further: you list this as WIP - do you see it as more or less usable in its current state, and how do you see the project's future?

@LiuJi-Jim
Copy link
Collaborator

Hi!

Thanks for trying and exploring this project!

@bytebase/vue-kbar is started as a part of our main project bytebase/bytebase. We are in our cycles to add more features to bytebase/bytebase. So now @bytebase/vue-kbar basically follows the need of bytebase/bytebase. Command palette might be an essential entrance of our global search-related features in the upcoming months. But it's still in the designing phase, and we cannot define what kind of feature we need to introduce by vue-kbar.

As you see, @bytebase/vue-kbar is now pretty feature-less and document-less. Your suggestions are really appreciated, and remind me that we should make a clear plan for the project.

We supported custom action sorting in v0.1.4, but unfortunately, I missed adding this feature to the README.

One thing I want to implement is dynamic item height. But we don't need this feature now in bytebase/bytebase, so it comes with relatively low priority.

I also consider that useKBarHandler returns a Ref<KBarHandler> making it somehow inconvenient to use. So I plan to change this API by returning an unwrapped KBarHandler. This will break the API, so it might be coming in the first major version.

I think the most important thing to me now is to make a demo website and better docs. In a couple of weeks maybe.

Thank you for your support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants