Module aws_sdk_honeycode::types
source · Expand description
Data structures used by operation inputs/outputs.
Modules§
- Builders
- Error types that Amazon Honeycode can respond with.
Structs§
An object that represents a single cell in a table.
CellInput object contains the data needed to create or update cells in a table.
Metadata for column in the table.
Data needed to create a single row in a table as part of the BatchCreateTableRows request.
The data in a particular data cell defined on the screen.
An object that contains the options relating to parsing delimited text as part of an import request.
An object that contains the options relating to the destination of the import request.
A single item in a batch that failed to perform the intended action because of an error preventing it from succeeding.
An object that represents a filter formula along with the id of the context row under which the filter function needs to evaluate.
An object that has details about the source of the data that was submitted for import.
An object that contains the configuration parameters for the data source of an import request.
An object that contains the attributes of the submitter of the import job.
An object that contains the options specified by the sumitter of the import request.
A single row in the ResultSet.
ResultSet contains the results of the request for a single block or list defined on the screen.
An object that contains the properties for importing data to a specific column in a table.
An object representing the properties of a table in a workbook.
An object that contains attributes about a single column in a table
The metadata associated with the table data import job that was submitted.
An object that contains attributes about a single row in a table
Data needed to create a single row in a table as part of the BatchCreateTableRows request.
Data needed to upsert rows in a table as part of a single item in the BatchUpsertTableRows request.
An object that represents the result of a single upsert row request.
The input variables to the app to be used by the InvokeScreenAutomation action request.
Enums§
- When writing a match expression against
ErrorCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Format
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ImportDataCharacterEncoding
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ImportSourceDataFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TableDataImportJobStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
UpsertAction
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.