DEPRECATION NOTICE: this package has been moved and improved at grizz-it/cli
This package contains elements for reading and writing in a CLI environment. It provides elements for easily rendering elements in a CLI environment. It supports creating CLI forms and even theming all of this.
To install the package run the following command:
composer require ulrack/cli
Elements implementing the ElementInterface, are a standard set of elements which render in a specific style to the user. These elements are fully customizable through theming (which will be covered later on).
The available elements are:
This is block for presenting content in a larger stage. It has configurable margins, paddings and colors.
The chain element itself is not an actual element, but an element to chain more elements into one, so this can be provided to methods which only accept one element.
The explained list element is an element that displays a nesting list of entries with a description. The element can be customized with colors. The items can be added by providing a description followed by a set of keys to determine the position in the list.
The form element is a wrapping element for rendering forms.
After it has been rendered once, the values can be retrieved with the getInput method.
The form element itself can not be customised, but the provided description can be styled.
The list element is a simple multi line renderer. It simply renders all items on a new line in a given style.
The progress element is used for displaying a progress bar.
This utilizes the TaskList from grizz-it/task to render.
The table element is a fully customizable (including the borders) table. It only renders the keys that have been defined of the array of items that is provided.
The textual element is a simple text element which can be customized using a style. It has the option to render a new line of the element or not.
The form elements are the elements used to render the form and retrieve input from the user.
There are two types of form elements provided in this package, which are Field. The field provides a simple one value form.
The other field type is an ArrayField. This field is used to receive multiple options from the user.
Both of these fields have customizable behaviour through their provided Reader.
Fields need to be accompanied by a FieldValidator, when they are provided to the form.
These validators are a combination of a Validator from the grizz-it/validator package and an element for rendering an error.
The IO namespace is used for Input and Output directly to and from the user.
Within the IO namespace Readers are used to record user input to provide information to the application.
The available readers are the following:
The error reader is used to always throw an error when reading is disabled. For example when an application uses a no interaction flag. This reader can be used to disable the interaction.
The Reader (standard reader) is a reader that uses the stdin from the CLI to read user input.
This reader uses (and expects) stty in the console to provide a layer over the stdin to provide an autocompleting experience.
It expects an OptionProvider to resolve the autocompletion options. A standard implementation is provided here.
This reader uses stty to remove the visibility of the input the user provides to the application.
This can be helpfull when the user has to provide a password.
The writer is used to output information to the user in the CLI directly. All output will be immediatly flushed to the user when a method is invoked.
The styler is used to output a style when writing to the output.
Styling can be applied by providing one or more enum values to the styler.
The options are defined in the StyleEnum.
To learn how to use enums, see the ulrack/enum package for more details.
The pointer class can be used to manipulate the pointer in the terminal. This can be usefull when overwriting text and rendering elements.
The terminal classes are used to determine the height and width of the terminal of the user.
This can be usefull when elements need to be rendered within the
bounds of the terminal.
There are two options provided with the package.
SttyTerminal uses stty to determine the size of the terminal.
TputTerminal uses tput to determine the size of the terminal.
Theming is used to differentiate the looks of elements used within the application.
Styles can be retrieved with the StyleEnum.
To learn how to use enums, see the grizz-it/enum package for more details.
These enum styles can be bound to a ConfigurableStyle to combine and render them.
These configurable styles can then be used in a Theme to unify the styling throughout the application. Theme also accept setting variables, so things like margin, padding and characters for elements can be configured as well.
An ApplicationTheme is provided with the package and shows the default values for all provided elements within the package. This theme can be found here.
For all these elements, factories have been made available.
For simplifying the creation of themes and forms two generators have been created.
These two classes provide method which support chaining for quickly generator a form and/or theme.
Examples can be found in the examples directory.
Please see CHANGELOG for more information on what has changed recently.
Please see CONTRIBUTING and CODE_OF_CONDUCT for details.
Copyright (c) GrizzIT
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.