We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently we have the option to show stage output in GUI tabs and/or print them as ASCII, giving rise to the following entry in default.json:
default.json
... "stage_output": { "default": "none", "title": "Show stage output", "type": "string", "enum": ["none", "tabs", "ascii", "tabs_and_ascii"], "enumDescriptions": ["None", "Tabs", "ASCII", "Tabs + ASCII"], "description": "Select how stage output should be displayed.", ...
Do we really need to print ASCII when we use the GUI? Furthermore we can not even show tabs from CLI.
{none, all, list} <-> {[], ["all"], ["list", "of", "stages"]}
none / []
This simplifies options for stage output considerably.
The text was updated successfully, but these errors were encountered:
Another idea: Given a stage name, print the previous and the given stage.
Sorry, something went wrong.
No branches or pull requests
Proposal
Currently we have the option to show stage output in GUI tabs and/or print them as ASCII, giving rise to the following entry in
default.json
:Do we really need to print ASCII when we use the GUI? Furthermore we can not even show tabs from CLI.
Approach
{none, all, list} <-> {[], ["all"], ["list", "of", "stages"]}
none / []
)This simplifies options for stage output considerably.
The text was updated successfully, but these errors were encountered: