You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When presenting a Select prompt, I would like the search/filter text to be pre-populated.
Describe the solution you'd like
A function like .with_predefined_text (like in the Editor prompt) or .with_initial_value (like in the Text prompt).
Maybe .with_predefined_search? Or maybe better to make it general, .with_predefined_input.
Describe alternatives you've considered
Alternative for my use case would be a Text prompt instead, and use the text entered to do a lookup in my data.
Edit: Took a stab at an implementation for my own usage #140
The text was updated successfully, but these errors were encountered:
On selects, display an initial list of values first
On customType/confirm, a suggestion or default value
The thing is that in these cases an initial value feels to me like the wrong solution to the problem it's trying to solve. It feels kind of clunky from the user-perspective if they have to delete this pre-filled value that's already there, like they're starting from a bad place already.
Adding it as an optional feature should be possible enough (as you already did on the PR), but before putting one extra knob I'm really interested in understanding if this knob is achieving the right thing
Sure, my scenario was a kind of http request REPL. Basically: first choose from a list of profiles (development, production, etc) then from a list of services (defined by openapi definitions) and then choose from a list of requests. Without prefilled input; to execute the same request multiple times one needed to search again to select it, and going back up, it was more natural for the previously selected thing to be selected already.
I radically changed the structure of the program so I do not really need this functionality for the execution of the request repeatedly anymore, but I think it is a nice change to make tha apis consistent and available for all different prompts.
Is your feature request related to a problem? Please describe.
When presenting a Select prompt, I would like the search/filter text to be pre-populated.
Describe the solution you'd like
A function like
.with_predefined_text
(like in the Editor prompt) or.with_initial_value
(like in the Text prompt).Maybe
.with_predefined_search
? Or maybe better to make it general,.with_predefined_input
.Describe alternatives you've considered
Alternative for my use case would be a Text prompt instead, and use the text entered to do a lookup in my data.
Edit: Took a stab at an implementation for my own usage #140
The text was updated successfully, but these errors were encountered: