Accept arbitrary string as input? about inquirer-autocomplete-prompt

[mhkeller]

This seems to be working. Did I miss anything? mhkeller@38c0f0a

[mokkabonna]

That was my thought as well. As you noticed this plugin currently forces you to choose a predefined one. But I also see the usefulness of being able to type anything you want. I was eventually planning to either support it with an option or create a stand alone plugin.

But don't know when I'll have the time to complete that, so if you create it, that is great!

Your changes seems to be the gist of it, although with your changes it seems that you only will be able to select something custom when the search string does not match anything. so you will not be able to enter "cookie" as a value if you have "cookie monster" in the list. Correct?

I would assume in such a plugin tabbing would autocomplete the selected choice, and enter would use whatever value you have typed, either your own or the autocompleted one.

Like so:

cookie => (tab) => cookie monster => (enter) => selects cookie monster
cookie => (enter) => cookie

Also, thanks for the interest and issue/PR reporting! I have had limited time to give this plugin enough love.

[mhkeller]

Ah ya I hadn't thought of that one. There might need to be a larger UI change in order to disambiguate when you want "cookie" to autocomplete to "Cookie Monster".

I don't have that use case currently. so for now I'll look at integrating this set up as an option and PR.

Le Nov 7, 2015 à 06:40, Martin Hansen [email protected] a écrit :

That was my thought as well. As you noticed this plugin currently forces you to choose a predefined one. But also see the usefulness of being able to type anything you want. Was eventually planning to either support it with an option or create a stand alone one.

But don't know when I'll have the time to complete that, so if you create it, that is great!

That looks like the gist of it, although with your changes it seems that you only will be able to select something custom when it does not match anything. so you will not be able to enter "cookie" as a value if you have "cookie monster" in the list. Correct?

—
Reply to this email directly or view it on GitHub.

[mhkeller]

I didn't see your flow layout above when I read this on my phone. Ya that seems reasonable although would "cookie monster" appear selected in the list after typing "cookie" before hitting tab?

Another way to do it is always display the arbitrary input in the list and preface it with some text or in a different style so the user knows it is not a part of the main list.

[Naramsim]

@mhkeller could you open a PR with your changes? So the users now are not forced to choose one option?

[Naramsim]

Or this PR does the same?
#9

[mokkabonna]

Closed in favor of #9 . It is now merged and published.