All Classes and Interfaces
Class
Description
As well as answering Questions in the wizard, the user can choose to perform
an action, such as saving their progress to file or displaying the current
pipeline status.
An
Asker for FunctionCallPrototypes that will ask extra questions if the chosen
aggregation function requires extra arguments for it's configuration.Provides a bridge between having a nice CLI UX (via the CompositeAsker) and
accepting any aggregate expression for the wizard questions (which simplifies
the config and means you can still do some advanced expression-y things with
a plain old wizard model).
Drives a
CliPrompter to make it easier for the user to answer it correctly for
a particular QuestionBrings together all the arguments to ask in to a single request-like object to make it easier to extend/tweak in the
future.
Default implementation
Base implementation of an Asker that cuts down on boiler plate and also binds the user's input (for validation
purposes) before returning the unbound value back to the survey (to make sure that it will bind and the UI isn't
doing some magic it's not allowed to - keep in mind that while this UI is part of the same process as the riskscape
engine, the wizard has been built so that it can work with a future web UI without huge amounts of re-work)
Asker for getting an answer that is a boolean yielding Expression, such as for a
filter condition.Comparison operators that are supported by the asker.
Represents the user choice in how to answer the attribute value part of the question, should there
be a lot of potential values in a list.
Used to represent a choice the user has to make as part of a prompt
High-level routines for interacting with the user to guide them through the wizard-answering process
Drives the wizard answering process on the CLI, this time for Survey2 surveys (rather than the old Survey) interface.
Compatibility shim to avoid having to change all the askers now that AskRequest exists
An
Asker for getting an Expression answer that allows the user to either enter the
expression themselves, or to build the expression interactively via
ExpressionAsker.askInteractively(nz.org.riskscape.wizard.CliPrompter, nz.org.riskscape.wizard.ExpressionHelper)Determines whether the user wants to provide a custom expression manually, or build an expression
interactively in the wizard.
Thrown by an
Action used as a sort of long jump (I know it's frowned upon, but it's the simplest way to
implement it) to signal the user chose undo from the ctrl-c menu.