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
Add text input component #9
Comments
I'm going to start working on this issue, is there anything that I should keep in mind? |
I think that the underlying generic for the text input should allow for some flexibility in terms of what can and will be built on top of it. For example, this will probably be the basis for numeric input, so there needs to be the option to add input validation. Just keep in mind that the base component should be as customizable as possible. |
Sounds good to me, checking if a string matches some format is going to be important. Something else I thought of which may be good to have is interchangeable prompting strings. Here's what I mean by that.
There should be two different options, one for the prompt and one for string which starts the input. |
I see I'll try to implement it so that it is set as an argument, and make like a default one as > or ↣ |
Yeah. For now, I'd go with > as the default. In the future my idea is to implement profiles of some sort which will change the default characters. I'd like them to be as consistent as possible throughout the package. For example, every arrow or pointer should be the same character. |
Create an interaction component which prompts the user and then takes input
The text was updated successfully, but these errors were encountered: