qoa
qoa copied to clipboard
Minimal interactive command-line prompts
**Describe the bug** When i put a color on a interactive input symbol, non-selected menus are not aligned anymore.  **To Reproduce** Just create a qoa.interactive input with a symbol...
We can use this form link https://forms.gle/6zoiq8jdagoMm9N48 to recommend @klaussinani for GitHub Sponsor Matching Funds Totaly worth for his work! 🚀 Original idea from https://github.com/klaussinani/ao/issues/96
Input validation. Fixes #5 Hello! This is a pull request implementing an input validation feature for, `input`, `hidden`, `secure` prompts. I ran `npm run test`, and there were no errors,...
## Description A prompt which allows users to select multiple options, inquirer already has this kind of prompt https://github.com/SBoudrias/Inquirer.js/#checkbox---type-checkbox  ## Solution? ```javascript const checklist = { type: 'checklist', query:...
**Describe the bug** qoa.interactive({ type: 'interactive', query: 'which code do you want to sync?', handle: 'type', symbol: '>', menu: [ 'react', 'vue' ] }); TypeError: this._input.setRawMode is not a function
`Separator for interactive` Fixes #6 Now menu items will look like below. ```js menu: [ 'outside walking', 'outside running', qoa.separator(), // qoa.separator({ separator: '---' }) default separator string pattern is...
Fixes #10 Added typescript support by declaring types for the exported `Qoa` API methods
## Description Add TypeScript support by declaring types for the exported Qoa API methods.
Please visit the [contributing guidelines](https://github.com/klaussinani/qoa/blob/master/contributing.md#translating-documentation) to learn more on how to translate Qoa's documentation into more languages. Tons of thank you to everyone for your help and support! ❤️
**Describe the bug** Not really a bug, just a developer question. I was developing a tool with Qoa, and I've done a typo in question type, `password` instead of `hidden`....