Form
Table of Contents
Namespaces
- Behavior
- Container
- Element
- Event
- Exception
- FieldControl
- FieldInformation
- FieldWizard
- FormDataGroup
- FormDataProvider
- NodeExpansion
- Processor
- Utility
- Wizard
Interfaces
- FormDataGroupInterface
- Interface must be implemented by form data group classes.
- FormDataProviderInterface
- Interface must be implemented by form data provider classes.
- NodeInterface
- Interface must be implemented by all container and widget classes
- NodeResolverInterface
- Interface must be implemented by node resolver classes
Classes
- AbstractNode
- Base class for container and single elements - their abstracts extend from here.
- Exception
- Generic backend form exception
- FormAction
- This is a helper class to understand when FormEngine should be doing something.
- FormDataCompiler
- Create and return a defined array of data ready to be used by the container / element render part of FormEngine
- FormResult
- Immutable value object carrying the rendering output of a single FormEngine element — its HTML fragment together with all page-level assets (JavaScript modules, stylesheets, language labels) the element needs to function.
- FormResultCollection
- Aggregates rendering results from multiple FormEngine elements and provides a deduplicated, merged view of all required page assets so they can be registered with the PageRenderer in a single pass.
- FormResultFactory
- Transforms the raw array returned by FormEngine node rendering into a typed FormResult value object.
- FormResultHandler
- Bridges FormEngine rendering and the PageRenderer by registering all scripts, styles, and language labels that FormEngine elements declared as dependencies, so the backend page can execute the rendered form.
- InlineStackProcessor
- Handle inline stack.
- NodeFactory
- Create an element object depending on renderType.