Structures

The actions property exposed on the CellConfigType represents possible events that will be executed based on the users interaction with that particular cell. Of note are the selectionAction and previewingViewControllerAction. The selectionAction is executed when the user taps on that particular cell. The main use case for this is present a new detail view controller or a modal (but is not constrained to these actions, these are just the common use cases). The previewingViewControllerAction is responsible for returning an instance of a UIViewController that will be shown when a user 3D-touches on a cell.

Defines the presentation information of an item inside a TableSection.

Some properties are only supported by UITableView.

Defines the view, state and layout information of a row item inside a TableSection. It relies on you to build UIView subclasses and use those instead of implementing UITableViewCell or UICollectionViewCell subclasses. This has the side effect of building better more reusable view components. This greatly simplifies composition by combining several host-cells into more complex layouts. It also makes equality simpler and more Swifty by requiring that anything provided as State only requires that the State object conform to the Equatable protocol. The View portion of the generic only requires it to be a UIView subclass.

Defines the style, and state information of a section.

FunctionalTableData deals in arrays of TableSection instances. Each section, at a minimum, has a string value unique within the table itself, and an array of CellConfigType instances that represent the rows of the section. Additionally there may be a header and footer for the section.