-
Notifications
You must be signed in to change notification settings - Fork 25
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
Split the question type and the application #14
Comments
@curry684 thx for your nice advice |
My use case is quite specific, I have a bunch of nested objects which can all be selected (leaves and nodes). Given a simple tree like this:
Selecting a target here is just more practical to present in a tree than with up to 3 consecutive questions, especially given that the user may not know beforehand where |
ok, I WILL wrok on it soon. |
That would be awesome :) It was just a suggestion because it seems you've already done all the hard work on showing a tree, splitting it out to have the file tree just as a "data source" to a generic tree handler shouldn't be hard methinks 😄 |
Given that this is the only inquirer plugin afaics that provides a tree based question - how about splitting it up in 2 packages
inquirer-tree-selection
and on top of that a thin layer for the filesystem?There are many more applications of trees than just filesystems.
The text was updated successfully, but these errors were encountered: