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
This is minor, but it does kind of irritate me: pressing "1" at the stage list selects stage 0, pressing "2" selects stage 1, and so on.
I've considered adding an "index" parameter to the question for inquirer to address this, but I'm not sure it's the most elegant solution - even though it'd solve my problem, I don't feel it'd be best of problems in general, so I'm choosing to just suck it up as-is for now. (If I used inquirer more, and had more use cases, I might implement a more robust reconfiguration, such as letting list selection be keyed-in by value, or having arbitrary key-in values, or showing values, or showing numbered indices...)
The text was updated successfully, but these errors were encountered:
Anyway, considering standard QWERTY keyboard number layout, this 1-indexing behavior is kind of most useful as-is, so... meh. Another reason I'm not really fighting this issue that much upstream.
This is minor, but it does kind of irritate me: pressing "1" at the stage list selects stage 0, pressing "2" selects stage 1, and so on.
I've considered adding an "index" parameter to the question for inquirer to address this, but I'm not sure it's the most elegant solution - even though it'd solve my problem, I don't feel it'd be best of problems in general, so I'm choosing to just suck it up as-is for now. (If I used inquirer more, and had more use cases, I might implement a more robust reconfiguration, such as letting list selection be keyed-in by value, or having arbitrary key-in values, or showing values, or showing numbered indices...)
The text was updated successfully, but these errors were encountered: