The furnace.actions vocabulary implements a type of responder, called an action, which handles the form validation lifecycle.
Other than form validation capability, actions are also often simpler to use than implementing new responders directly, since creating a new class is not required, and the action dispatches on the request type (GET, HEAD, or POST).
The class of actions:
Creating a new action:
Once created, an action needs to be configured; typically the creation and configuration of an action is encapsulated into a single word:
Furnace action configuration
Validating forms with actions:
Form validation with actions
More about the form validation lifecycle:
Furnace action lifecycle
A convenience class:
Furnace page actions
Low-level features:
Furnace actions implementation
Other than form validation capability, actions are also often simpler to use than implementing new responders directly, since creating a new class is not required, and the action dispatches on the request type (GET, HEAD, or POST).
The class of actions:
action
Creating a new action:
<action> ( -- action )
Once created, an action needs to be configured; typically the creation and configuration of an action is encapsulated into a single word:
Furnace action configurationValidating forms with actions:
Form validation with actionsMore about the form validation lifecycle:
Furnace action lifecycleA convenience class:
Furnace page actionsLow-level features:
Furnace actions implementation